Project Number Date
test_Tails_ISO_stable 5555 05 Apr 2025, 09:10

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 19:53.574 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
2:22.218
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 29.599
When I start Tails from USB drive "old" with network unplugged 1:47.063
Then the boot device has safe access rights 3.181
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.127
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:330 8.898
After features/support/hooks.rb:100 0.009
Tags: @product
2:23.204
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:35.175
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 36.662
And I take note of which tps features are available 1.795
Then a Tails persistence partition exists on USB drive "old" 0.716
And I shutdown Tails and wait for the computer to power off 8.272
After features/support/hooks.rb:330 0.184
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.689
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.838
Then Tails is running from USB drive "old" 0.458
And all tps features are active 1.964
When I write some files expected to persist 1.676
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 2.480
And I take note of which tps features are available 0.441
And I shutdown Tails and wait for the computer to power off 4.581
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.328
After features/support/hooks.rb:330 0.104
After features/support/hooks.rb:100 0.007
Tags: @product
2:31.464
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.463
And I log in to a new session 18.841
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.622
And I plug USB drive "to_upgrade" 2.400
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.170
Then the running Tails is installed on USB drive "to_upgrade" 25.553
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:330 1.122
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.473
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.991
Then all tps features from the old Tails version are active 1.556
And Tails is running from USB drive "to_upgrade" 0.385
And the boot device has safe access rights 3.344
And the expected persistent files created with the old Tails version are present in the filesystem 1.417
And all persistent directories from the old Tails version have safe access rights 2.559
After features/support/hooks.rb:330 0.756
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:45.290
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.536
And no SquashFS delta is installed 0.197
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.158
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.307
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.556
When the network is plugged 0.068
And Tor is ready 20.875
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.159
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.705
Given I shutdown Tails and wait for the computer to power off 8.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.095
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.419
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.390
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.084
And Tor is ready 21.540
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.334
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.782
Given I shutdown Tails and wait for the computer to power off 4.366
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.822
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.074
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.423
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.352
When the network is plugged 0.070
And Tor is ready 16.086
Then the Upgrader considers the system as up-to-date 11.127
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 17.530
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.213
After features/support/hooks.rb:330 0.663
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.234
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.366
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.559
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the signing key used by the Upgrader is outdated 0.116
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 23.798
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.197
After features/support/hooks.rb:330 1.081
After features/support/hooks.rb:100 0.000