Project Number Date
test_Tails_ISO_stable 6280 09 Apr 2026, 00:07

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 12:35.036 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
1:10.705
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 13.454
When I start Tails from USB drive "old" with network unplugged 52.899
Then the boot device has safe access rights 2.542
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:331 1.208
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.005
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 53.115
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 23.577
And I take note of which tps features are available 0.628
Then a Tails persistence partition exists on USB drive "old" 0.497
And I shutdown Tails and wait for the computer to power off 7.879
After features/support/hooks.rb:331 0.409
After features/support/hooks.rb:100 0.007
Tags: @product
1:21.570
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.166
Then Tails is running from USB drive "old" 0.278
And all tps features are active 1.145
When I write some files expected to persist 1.185
# 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.452
And all persistent directories from the old Tails version have safe access rights 1.791
And I take note of which tps features are available 0.164
And I shutdown Tails and wait for the computer to power off 4.026
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.120
After features/support/hooks.rb:331 0.254
After features/support/hooks.rb:100 0.007
Tags: @product
2:18.632
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 without a persistent partition and stopped at Tails Greeter's login screen 8.307
And I log in to a new session 17.074
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.638
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.877
Then the running Tails is installed on USB drive "to_upgrade" 16.222
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:331 3.691
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.854
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.981
Then all tps features from the old Tails version are active 0.926
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.508
And the expected persistent files created with the old Tails version are present in the filesystem 1.106
And all persistent directories from the old Tails version have safe access rights 2.056
After features/support/hooks.rb:331 0.973
After features/support/hooks.rb:100 0.038
4:34.847
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 8.985
And no SquashFS delta is installed 0.136
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.518
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.377
When the network is plugged 0.029
And Tor is ready 20.859
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.359
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.399
Given I shutdown Tails and wait for the computer to power off 20.758
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.957
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.197
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
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.160
# 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.171
When the network is plugged 0.013
And Tor is ready 22.539
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.740
Given I shutdown Tails and wait for the computer to power off 16.972
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.192
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.127
And the file system changes introduced in version 6.3~testoverlayfs are present 0.375
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.023
And Tor is ready 21.085
Then the Upgrader considers the system as up-to-date 0.097
# 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 4.159
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.348
After features/support/hooks.rb:331 0.701
After features/support/hooks.rb:100 0.010
30.421
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.585
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 22.100
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.347
After features/support/hooks.rb:331 0.861
After features/support/hooks.rb:100 0.000