Project Number Date
test_Tails_ISO_stable 5727 19 Jun 2025, 12:43

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:30.264 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:6.464
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.835
When I start Tails from USB drive "old" with network unplugged 1:29.968
Then the boot device has safe access rights 3.087
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.481
And I unplug USB drive "old" 0.280
After features/support/hooks.rb:330 3.649
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.544
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:26.716
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 31.963
And I take note of which tps features are available 1.984
Then a Tails persistence partition exists on USB drive "old" 0.743
And I shutdown Tails and wait for the computer to power off 8.611
After features/support/hooks.rb:330 0.162
After features/support/hooks.rb:100 0.010
Tags: @product
3:3.267
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.009
Then Tails is running from USB drive "old" 0.298
And all tps features are active 2.083
When I write some files expected to persist 1.728
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.580
And all persistent directories from the old Tails version have safe access rights 2.915
And I take note of which tps features are available 0.464
And I shutdown Tails and wait for the computer to power off 6.713
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.001
After features/support/hooks.rb:330 0.116
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.704
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.355
And I log in to a new session 19.573
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.711
And I plug USB drive "to_upgrade" 2.354
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.549
Then the running Tails is installed on USB drive "to_upgrade" 27.746
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:330 7.210
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.290
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.381
Then all tps features from the old Tails version are active 1.845
And Tails is running from USB drive "to_upgrade" 0.398
And the boot device has safe access rights 3.405
And the expected persistent files created with the old Tails version are present in the filesystem 1.493
And all persistent directories from the old Tails version have safe access rights 2.582
After features/support/hooks.rb:330 0.779
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:28.597
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.164
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.367
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.799
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.442
When the network is plugged 0.097
And Tor is ready 19.382
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.159
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.221
Given I shutdown Tails and wait for the computer to power off 9.433
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.365
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 1.948
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.267
When the network is plugged 0.062
And Tor is ready 20.656
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.433
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.036
Given I shutdown Tails and wait for the computer to power off 4.217
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.251
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.422
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.119
And Tor is ready 18.692
Then the Upgrader considers the system as up-to-date 0.320
# 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 15.171
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.496
After features/support/hooks.rb:330 0.745
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
37.395
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.231
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.130
And the signing key used by the Upgrader is outdated 0.092
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 18.500
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.040
After features/support/hooks.rb:330 0.851
After features/support/hooks.rb:100 0.000