Project Number Date
test_Tails_ISO_stable 6001 11 Dec 2025, 08:11

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 15:53.037 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:4.450
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 32.347
When I start Tails from USB drive "old" with network unplugged 1:26.065
Then the boot device has safe access rights 3.839
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.248
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:331 3.896
After features/support/hooks.rb:100 0.017
Tags: @product
2:2.655
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:25.388
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 31.325
And I take note of which tps features are available 1.467
Then a Tails persistence partition exists on USB drive "old" 0.744
And I shutdown Tails and wait for the computer to power off 3.240
After features/support/hooks.rb:331 0.337
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.223
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:35.227
Then Tails is running from USB drive "old" 0.728
And all tps features are active 1.840
When I write some files expected to persist 1.511
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 2.168
And I take note of which tps features are available 0.423
And I shutdown Tails and wait for the computer to power off 7.654
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.979
After features/support/hooks.rb:331 0.312
After features/support/hooks.rb:100 0.014
Tags: @product
2:41.558
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 14.704
And I log in to a new session 18.060
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.886
And I plug USB drive "to_upgrade" 2.516
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.078
Then the running Tails is installed on USB drive "to_upgrade" 20.836
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.252
After features/support/hooks.rb:331 6.513
After features/support/hooks.rb:100 0.000
Tags: @product
1:25.654
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.853
Then all tps features from the old Tails version are active 2.619
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.260
And the expected persistent files created with the old Tails version are present in the filesystem 1.267
And all persistent directories from the old Tails version have safe access rights 2.135
After features/support/hooks.rb:331 0.953
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:4.605
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 with a persistent partition enabled and logged in 20.318
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.125
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.058
And Tor is ready 44.075
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.633
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.192
Given I shutdown Tails and wait for the computer to power off 11.340
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.841
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.560
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.258
When the network is plugged 0.053
And Tor is ready 12.903
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.829
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.855
Given I shutdown Tails and wait for the computer to power off 8.029
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.478
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.134
And the file system changes introduced in version 6.3~testoverlayfs are present 0.590
And only the 6.3~testoverlayfs SquashFS delta is installed 0.124
# 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.224
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.200
And Tor is ready 12.147
Then the Upgrader considers the system as up-to-date 0.120
# 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 5.864
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.735
After features/support/hooks.rb:331 1.342
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
24.890
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.911
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 10.565
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.963
After features/support/hooks.rb:331 1.011
After features/support/hooks.rb:100 0.000