Project Number Date
test_Tails_ISO_codespell 15 29 Jun 2025, 10:58

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 26:32.344 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:58.874
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given a computer 0.336
And I create a 7200 MiB disk named "old" 0.121
And I plug USB drive "old" 1.091
And I write an old version of the Tails USB image to disk "old" 41.712
When I start Tails from USB drive "old" with network unplugged 2:4.711
Then the boot device has safe access rights 4.172
And Tails is running from USB drive "old" 2.016
And there is no persistence partition on USB drive "old" 0.164
And process "udev-watchdog" is running 0.255
And udev-watchdog is monitoring the correct device 1.399
And I unplug USB drive "old" 2.894
After features/support/hooks.rb:330 5.258
After features/support/hooks.rb:100 0.064
Tags: @product
3:2.822
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 2:4.385
Then Tails is running from USB drive "old" 0.819
And I create a persistent partition 40.961
And I take note of which tps features are available 4.058
Then a Tails persistence partition exists on USB drive "old" 2.757
And I shutdown Tails and wait for the computer to power off 9.626
After features/support/hooks.rb:330 0.213
After features/support/hooks.rb:100 0.007
Tags: @product
3:54.495
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.299
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:55.387
Then Tails is running from USB drive "old" 1.055
And all tps features are active 2.028
When I write some files expected to persist 2.505
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.388
And all persistence configuration files have safe access rights 0.456
And all persistent directories from the old Tails version have safe access rights 6.038
And I take note of which tps features are available 0.749
And I shutdown Tails and wait for the computer to power off 7.342
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 38.244
After features/support/hooks.rb:330 0.162
After features/support/hooks.rb:100 0.012
Tags: @product
3:16.973
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 without a persistent partition and stopped at Tails Greeter's login screen 10.896
And I log in to a new session 30.880
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.489
And I plug USB drive "to_upgrade" 3.703
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.139
Then the running Tails is installed on USB drive "to_upgrade" 37.815
And I unplug USB drive "to_upgrade" 0.416
And I unplug USB drive "__internal" 0.630
After features/support/hooks.rb:330 3.596
After features/support/hooks.rb:100 0.000
Tags: @product
3:19.340
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:2.226
Then all tps features from the old Tails version are active 2.314
And Tails is running from USB drive "to_upgrade" 0.585
And the boot device has safe access rights 7.270
And the expected persistent files created with the old Tails version are present in the filesystem 3.306
And all persistent directories from the old Tails version have safe access rights 3.432
After features/support/hooks.rb:330 0.736
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
9:5.052
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 13.623
And no SquashFS delta is installed 0.148
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.484
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.208
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.477
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.740
When the network is plugged 0.147
And Tor is ready 27.089
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.684
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 20.698
Given I shutdown Tails and wait for the computer to power off 11.149
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:8.312
Then Tails is running version 6.2~testoverlayfs 0.031
And all tps features are active 3.362
And the file system changes introduced in version 6.2~testoverlayfs are present 0.464
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.368
When the network is plugged 0.080
And Tor is ready 23.326
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 10.700
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.472
Given I shutdown Tails and wait for the computer to power off 9.373
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:42.646
Then Tails is running version 6.3~testoverlayfs 0.035
And all tps features are active 2.464
And the file system changes introduced in version 6.3~testoverlayfs are present 0.533
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.067
And Tor is ready 21.111
Then the Upgrader considers the system as up-to-date 0.338
# 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 19.896
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.902
After features/support/hooks.rb:330 0.996
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
54.786
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 16.940
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.126
And Tor is ready 30.843
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.367
After features/support/hooks.rb:330 0.682
After features/support/hooks.rb:100 0.000