Project Number Date
test_Tails_ISO_stable 6566 08 Aug 2026, 11:46

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:45.004 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.916
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.100
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.880
When I start Tails from USB drive "old" with network unplugged 52.681
Then the boot device has safe access rights 2.624
And Tails is running from USB drive "old" 0.224
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.171
And I unplug USB drive "old" 0.110
After features/support/hooks.rb:339 3.883
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.816
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login 49.759
Then Tails is running from USB drive "old" 0.255
And I create a persistent partition 23.297
And I take note of which tps features are available 6.696
Then a Tails persistence partition exists on USB drive "old" 0.573
And I shutdown Tails and wait for the computer to power off 4.122
After features/support/hooks.rb:339 0.559
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.971
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.534
Then Tails is running from USB drive "old" 0.256
And all tps features are active 7.681
When I write some files expected to persist 1.288
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.277
And all persistent directories from the old Tails version have safe access rights 2.158
And I take note of which tps features are available 6.540
And I shutdown Tails and wait for the computer to power off 2.598
# 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.394
After features/support/hooks.rb:339 0.298
After features/support/hooks.rb:108 0.005
Tags: @product
2:15.265
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.503
And I log in to a new session 12.404
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.798
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.608
Then the running Tails is installed on USB drive "to_upgrade" 19.459
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 4.142
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.719
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.091
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.479
Then all tps features from the old Tails version are active 1.082
And Tails is running from USB drive "to_upgrade" 0.193
And the boot device has safe access rights 2.137
And the expected persistent files created with the old Tails version are present in the filesystem 0.886
And all persistent directories from the old Tails version have safe access rights 1.847
After features/support/hooks.rb:339 0.455
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:46.409
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.990
And no SquashFS delta is installed 0.160
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
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.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.444
When the network is plugged 0.028
And Tor is ready 12.304
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.085
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.310
Given I shutdown Tails and wait for the computer to power off 5.272
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.089
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 12.194
And the file system changes introduced in version 6.2~testoverlayfs are present 0.187
And only the 6.2~testoverlayfs SquashFS delta is installed 0.033
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.088
# 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.176
When the network is plugged 0.041
And Tor is ready 11.149
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.061
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.985
Given I shutdown Tails and wait for the computer to power off 4.060
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.876
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.336
And the file system changes introduced in version 6.3~testoverlayfs are present 0.344
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.025
And Tor is ready 10.447
Then the Upgrader considers the system as up-to-date 0.149
# 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.297
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.413
After features/support/hooks.rb:339 0.938
After features/support/hooks.rb:108 0.024
Tags: @product @automatic_upgrade
20.905
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.461
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.033
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 10.352
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.767
After features/support/hooks.rb:339 0.862
After features/support/hooks.rb:108 0.000