Project Number Date
test_Tails_ISO_stable 5766 14 Jul 2025, 18:31

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 23:44.671 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:26.175
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.164
When I start Tails from USB drive "old" with network unplugged 1:48.132
Then the boot device has safe access rights 3.506
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:330 4.264
After features/support/hooks.rb:100 0.084
Tags: @product
2:31.874
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.042
Given a computer 0.291
And I start Tails from USB drive "old" with network unplugged and I login 1:42.478
Then Tails is running from USB drive "old" 0.401
And I create a persistent partition 34.795
And I take note of which tps features are available 3.372
Then a Tails persistence partition exists on USB drive "old" 1.239
And I shutdown Tails and wait for the computer to power off 9.295
After features/support/hooks.rb:330 0.180
After features/support/hooks.rb:100 0.008
Tags: @product
3:30.849
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:43.282
Then Tails is running from USB drive "old" 0.462
And all tps features are active 2.794
When I write some files expected to persist 2.437
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.366
And all persistence configuration files have safe access rights 0.568
And all persistent directories from the old Tails version have safe access rights 3.594
And I take note of which tps features are available 0.647
And I shutdown Tails and wait for the computer to power off 6.131
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 30.383
After features/support/hooks.rb:330 0.401
After features/support/hooks.rb:100 0.047
Tags: @product
2:53.564
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.686
And I log in to a new session 23.610
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.878
And I plug USB drive "to_upgrade" 2.521
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.637
Then the running Tails is installed on USB drive "to_upgrade" 32.838
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:330 3.687
After features/support/hooks.rb:100 0.000
Tags: @product
2:54.568
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.320
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:43.633
Then all tps features from the old Tails version are active 2.057
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.646
And the expected persistent files created with the old Tails version are present in the filesystem 1.483
And all persistent directories from the old Tails version have safe access rights 3.077
After features/support/hooks.rb:330 1.769
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:43.313
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.017
And no SquashFS delta is installed 0.351
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.633
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.332
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.552
When the network is plugged 0.135
And Tor is ready 27.650
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.280
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.922
Given I shutdown Tails and wait for the computer to power off 12.197
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.989
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 4.202
And the file system changes introduced in version 6.2~testoverlayfs are present 0.655
And only the 6.2~testoverlayfs SquashFS delta is installed 0.113
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.592
# 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.534
When the network is plugged 0.073
And Tor is ready 18.546
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.168
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.173
Given I shutdown Tails and wait for the computer to power off 1:8.421
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.833
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 2.322
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.101
And Tor is ready 22.519
Then the Upgrader considers the system as up-to-date 0.460
# 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 16.873
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.381
After features/support/hooks.rb:330 0.896
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
44.325
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 10.762
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the signing key used by the Upgrader is outdated 0.150
But a current signing key is available on our website 0.000
When the network is plugged 0.149
And Tor is ready 23.399
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.414
After features/support/hooks.rb:330 1.165
After features/support/hooks.rb:100 0.000