Project Number Date
test_Tails_ISO_stable 6625 02 Sep 2026, 13:18

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 11:56.006 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:11.877
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.740
When I start Tails from USB drive "old" with network unplugged 52.500
Then the boot device has safe access rights 2.814
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 3.674
After features/support/hooks.rb:108 0.007
Tags: @product
1:27.888
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login 51.551
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 24.589
And I take note of which tps features are available 6.553
Then a Tails persistence partition exists on USB drive "old" 0.616
And I shutdown Tails and wait for the computer to power off 4.207
After features/support/hooks.rb:339 0.505
After features/support/hooks.rb:108 0.021
Tags: @product
1:38.851
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.100
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.351
Then Tails is running from USB drive "old" 0.266
And all tps features are active 8.072
When I write some files expected to persist 1.321
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.301
And all persistent directories from the old Tails version have safe access rights 2.033
And I take note of which tps features are available 6.927
And I shutdown Tails and wait for the computer to power off 4.210
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.091
After features/support/hooks.rb:339 0.439
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.028
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.830
And I log in to a new session 12.479
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.998
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.115
Then the running Tails is installed on USB drive "to_upgrade" 19.132
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:339 3.897
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.316
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.380
Then all tps features from the old Tails version are active 1.061
And Tails is running from USB drive "to_upgrade" 0.208
And the boot device has safe access rights 1.950
And the expected persistent files created with the old Tails version are present in the filesystem 0.933
And all persistent directories from the old Tails version have safe access rights 1.696
After features/support/hooks.rb:339 0.920
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:49.577
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.632
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.201
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.403
When the network is plugged 0.039
And Tor is ready 12.582
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.342
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.828
Given I shutdown Tails and wait for the computer to power off 5.683
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.312
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.390
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.122
# 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.189
When the network is plugged 0.024
And Tor is ready 11.126
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.409
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.772
Given I shutdown Tails and wait for the computer to power off 4.268
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.087
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 8.900
And the file system changes introduced in version 6.3~testoverlayfs are present 0.387
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.112
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.223
When the network is plugged 0.042
And Tor is ready 10.501
Then the Upgrader considers the system as up-to-date 0.126
# 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 3.747
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.356
After features/support/hooks.rb:339 0.897
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
19.466
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.479
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 8.894
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.702
After features/support/hooks.rb:339 0.779
After features/support/hooks.rb:108 0.000