Project Number Date
test_Tails_ISO_stable 6749 15 Oct 2026, 11:29

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 10:56.579 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:3.999
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.157
When I start Tails from USB drive "old" with network unplugged 47.274
Then the boot device has safe access rights 1.944
And Tails is running from USB drive "old" 0.141
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.038
And udev-watchdog is monitoring the correct device 0.156
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 3.558
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.883
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 45.827
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 22.885
And I take note of which tps features are available 6.272
Then a Tails persistence partition exists on USB drive "old" 0.515
And I shutdown Tails and wait for the computer to power off 4.078
After features/support/hooks.rb:339 0.426
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.213
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.310
Then Tails is running from USB drive "old" 0.217
And all tps features are active 6.725
When I write some files expected to persist 0.993
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.140
And all persistence configuration files have safe access rights 0.244
And all persistent directories from the old Tails version have safe access rights 1.391
And I take note of which tps features are available 5.966
And I shutdown Tails and wait for the computer to power off 3.964
# 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" 11.170
After features/support/hooks.rb:339 0.589
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.413
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 without a persistent partition and stopped at Tails Greeter's login screen 8.184
And I log in to a new session 10.660
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.590
And I plug USB drive "to_upgrade" 2.182
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.115
Then the running Tails is installed on USB drive "to_upgrade" 17.407
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.156
After features/support/hooks.rb:339 1.653
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.271
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 57.657
Then all tps features from the old Tails version are active 0.998
And Tails is running from USB drive "to_upgrade" 0.157
And the boot device has safe access rights 2.105
And the expected persistent files created with the old Tails version are present in the filesystem 0.841
And all persistent directories from the old Tails version have safe access rights 1.431
After features/support/hooks.rb:339 0.896
After features/support/hooks.rb:108 0.005
3:32.250
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 20.811
And no SquashFS delta is installed 0.047
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.168
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.148
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.282
When the network is plugged 0.028
And Tor is ready 13.095
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.327
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.260
Given I shutdown Tails and wait for the computer to power off 5.241
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.019
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.550
And the file system changes introduced in version 6.2~testoverlayfs are present 0.200
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.114
# 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.147
When the network is plugged 0.033
And Tor is ready 10.147
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.296
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.522
Given I shutdown Tails and wait for the computer to power off 3.981
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.967
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.530
And the file system changes introduced in version 6.3~testoverlayfs are present 0.276
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.091
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.144
When the network is plugged 0.035
And Tor is ready 10.144
Then the Upgrader considers the system as up-to-date 0.082
# 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.128
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.297
After features/support/hooks.rb:339 0.534
After features/support/hooks.rb:108 0.009
19.547
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 7.703
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.183
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 9.610
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.907
After features/support/hooks.rb:339 0.571
After features/support/hooks.rb:108 0.000