Project Number Date
test_Tails_ISO_stable 6532 27 Jul 2026, 11:49

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:9.886 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:15.918
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.578
When I start Tails from USB drive "old" with network unplugged 57.644
Then the boot device has safe access rights 2.869
And Tails is running from USB drive "old" 0.257
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.159
After features/support/hooks.rb:339 1.502
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.517
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 55.701
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 23.778
And I take note of which tps features are available 4.145
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 4.058
After features/support/hooks.rb:339 0.367
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.080
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.697
Then Tails is running from USB drive "old" 0.282
And all tps features are active 5.233
When I write some files expected to persist 1.285
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.156
And all persistence configuration files have safe access rights 0.323
And all persistent directories from the old Tails version have safe access rights 1.829
And I take note of which tps features are available 3.762
And I shutdown Tails and wait for the computer to power off 4.452
# 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.995
After features/support/hooks.rb:339 0.292
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.711
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.131
And I log in to a new session 13.843
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.770
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.345
Then the running Tails is installed on USB drive "to_upgrade" 16.068
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.151
After features/support/hooks.rb:339 0.912
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.331
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.044
Then all tps features from the old Tails version are active 0.993
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.483
And the expected persistent files created with the old Tails version are present in the filesystem 1.317
And all persistent directories from the old Tails version have safe access rights 2.183
After features/support/hooks.rb:339 0.951
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:59.602
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.137
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.013
And Tor is ready 12.816
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.471
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.300
Given I shutdown Tails and wait for the computer to power off 6.954
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.889
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.944
And the file system changes introduced in version 6.2~testoverlayfs are present 0.224
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.236
When the network is plugged 0.016
And Tor is ready 10.278
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.716
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.230
Given I shutdown Tails and wait for the computer to power off 4.094
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.007
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.135
And the file system changes introduced in version 6.3~testoverlayfs are present 0.400
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.180
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.194
When the network is plugged 0.021
And Tor is ready 10.415
Then the Upgrader considers the system as up-to-date 10.560
# 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.710
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.446
After features/support/hooks.rb:339 0.856
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
21.724
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 7.788
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.606
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.929
After features/support/hooks.rb:339 1.039
After features/support/hooks.rb:108 0.000