Project Number Date
test_Tails_ISO_devel 4109 09 Dec 2025, 13:05

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:43.745 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:2.828
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.261
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 32.803
When I start Tails from USB drive "old" with network unplugged 1:24.063
Then the boot device has safe access rights 3.619
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.112
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:331 4.080
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.680
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:25.347
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 29.101
And I take note of which tps features are available 1.246
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 7.674
After features/support/hooks.rb:331 0.303
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.836
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:35.703
Then Tails is running from USB drive "old" 0.703
And all tps features are active 1.934
When I write some files expected to persist 1.478
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.312
And all persistent directories from the old Tails version have safe access rights 2.166
And I take note of which tps features are available 0.478
And I shutdown Tails and wait for the computer to power off 4.915
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.778
After features/support/hooks.rb:331 0.564
After features/support/hooks.rb:100 0.009
Tags: @product
2:42.692
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 11.784
And I log in to a new session 15.834
And I clone USB drive "old" to a new USB drive "to_upgrade" 8.884
And I plug USB drive "to_upgrade" 2.781
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.629
Then the running Tails is installed on USB drive "to_upgrade" 20.343
And I unplug USB drive "to_upgrade" 0.245
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:331 3.859
After features/support/hooks.rb:100 0.000
Tags: @product
1:28.635
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:19.382
Then all tps features from the old Tails version are active 2.043
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.166
And the expected persistent files created with the old Tails version are present in the filesystem 1.364
And all persistent directories from the old Tails version have safe access rights 2.142
After features/support/hooks.rb:331 0.824
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:52.856
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.440
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.454
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.487
When the network is plugged 0.057
And Tor is ready 15.667
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.630
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.667
Given I shutdown Tails and wait for the computer to power off 11.668
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.357
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.266
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.163
# 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.248
When the network is plugged 0.065
And Tor is ready 11.663
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.279
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.088
Given I shutdown Tails and wait for the computer to power off 7.957
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.496
Then Tails is running version 6.3~testoverlayfs 0.038
And all tps features are active 2.236
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.079
# 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.172
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.078
And Tor is ready 42.134
Then the Upgrader considers the system as up-to-date 0.168
# 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 6.233
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.459
After features/support/hooks.rb:331 0.948
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
26.215
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 11.617
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
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.074
And Tor is ready 12.401
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.694
After features/support/hooks.rb:331 1.152
After features/support/hooks.rb:100 0.000