Project Number Date
test_Tails_ISO_stable 6602 22 Aug 2026, 11:27

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:47.970 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:7.868
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.104
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.905
When I start Tails from USB drive "old" with network unplugged 51.253
Then the boot device has safe access rights 2.036
And Tails is running from USB drive "old" 0.176
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.134
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:339 3.656
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.073
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 46.332
Then Tails is running from USB drive "old" 0.208
And I create a persistent partition 22.301
And I take note of which tps features are available 6.076
Then a Tails persistence partition exists on USB drive "old" 0.517
And I shutdown Tails and wait for the computer to power off 2.563
After features/support/hooks.rb:339 0.221
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.116
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.875
Then Tails is running from USB drive "old" 0.216
And all tps features are active 6.505
When I write some files expected to persist 0.907
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.123
And all persistence configuration files have safe access rights 0.250
And all persistent directories from the old Tails version have safe access rights 1.676
And I take note of which tps features are available 6.209
And I shutdown Tails and wait for the computer to power off 2.512
# 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" 10.750
After features/support/hooks.rb:339 0.267
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.266
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 7.935
And I log in to a new session 10.653
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.549
And I plug USB drive "to_upgrade" 2.271
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.188
Then the running Tails is installed on USB drive "to_upgrade" 17.427
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.674
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.936
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.903
Then all tps features from the old Tails version are active 1.002
And Tails is running from USB drive "to_upgrade" 0.218
And the boot device has safe access rights 2.045
And the expected persistent files created with the old Tails version are present in the filesystem 1.048
And all persistent directories from the old Tails version have safe access rights 1.643
After features/support/hooks.rb:339 0.722
After features/support/hooks.rb:108 0.006
3:21.095
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.062
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.249
When the network is plugged 0.040
And Tor is ready 11.609
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.274
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.745
Given I shutdown Tails and wait for the computer to power off 5.309
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.103
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 7.617
And the file system changes introduced in version 6.2~testoverlayfs are present 0.197
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# 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.158
When the network is plugged 0.031
And Tor is ready 10.082
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.293
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.309
Given I shutdown Tails and wait for the computer to power off 2.583
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.133
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.236
And the file system changes introduced in version 6.3~testoverlayfs are present 0.397
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.099
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.033
And Tor is ready 10.070
Then the Upgrader considers the system as up-to-date 0.080
# 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.102
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.300
After features/support/hooks.rb:339 0.771
After features/support/hooks.rb:108 0.009
17.614
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.868
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 9.114
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.310
After features/support/hooks.rb:339 0.528
After features/support/hooks.rb:108 0.000