Project Number Date
test_Tails_ISO_stable 5609 29 Apr 2025, 13:08

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:58.149 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:28.753
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 31.604
When I start Tails from USB drive "old" with network unplugged 1:51.534
Then the boot device has safe access rights 3.266
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:330 3.755
After features/support/hooks.rb:100 0.011
Tags: @product
2:12.446
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:29.046
Then Tails is running from USB drive "old" 0.334
And I create a persistent partition 30.974
And I take note of which tps features are available 2.525
Then a Tails persistence partition exists on USB drive "old" 0.848
And I shutdown Tails and wait for the computer to power off 8.527
After features/support/hooks.rb:330 0.174
After features/support/hooks.rb:100 0.010
Tags: @product
2:54.148
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.283
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.619
Then Tails is running from USB drive "old" 0.377
And all tps features are active 2.110
When I write some files expected to persist 2.151
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.441
And all persistent directories from the old Tails version have safe access rights 2.448
And I take note of which tps features are available 0.516
And I shutdown Tails and wait for the computer to power off 4.502
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.463
After features/support/hooks.rb:330 0.128
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.924
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 without a persistent partition and stopped at Tails Greeter's login screen 10.049
And I log in to a new session 17.832
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.664
And I plug USB drive "to_upgrade" 2.420
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.651
Then the running Tails is installed on USB drive "to_upgrade" 22.912
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:330 0.988
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.993
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.440
Then all tps features from the old Tails version are active 1.875
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.244
And the expected persistent files created with the old Tails version are present in the filesystem 1.482
And all persistent directories from the old Tails version have safe access rights 2.439
After features/support/hooks.rb:330 1.348
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:55.462
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.866
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.609
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.409
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.521
When the network is plugged 0.084
And Tor is ready 18.363
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.942
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.035
Given I shutdown Tails and wait for the computer to power off 10.961
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.575
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.227
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.393
# 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.272
When the network is plugged 0.057
And Tor is ready 19.799
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.294
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.331
Given I shutdown Tails and wait for the computer to power off 6.511
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.974
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.295
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.257
When the network is plugged 0.067
And Tor is ready 47.112
Then the Upgrader considers the system as up-to-date 0.318
# 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.902
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.836
After features/support/hooks.rb:330 0.709
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.420
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 9.942
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 17.820
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.118
After features/support/hooks.rb:330 1.542
After features/support/hooks.rb:100 0.000