Project Number Date
test_Tails_ISO_stable 6646 08 Sep 2026, 11:44

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:55.302 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:19.119
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
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" 13.560
When I start Tails from USB drive "old" with network unplugged 1:1.434
Then the boot device has safe access rights 2.374
And Tails is running from USB drive "old" 0.216
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 1.165
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.682
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login 50.587
Then Tails is running from USB drive "old" 0.191
And I create a persistent partition 24.094
And I take note of which tps features are available 7.882
Then a Tails persistence partition exists on USB drive "old" 0.589
And I shutdown Tails and wait for the computer to power off 4.242
After features/support/hooks.rb:339 0.170
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.322
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.197
Then Tails is running from USB drive "old" 0.226
And all tps features are active 7.863
When I write some files expected to persist 1.351
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.141
And all persistence configuration files have safe access rights 0.293
And all persistent directories from the old Tails version have safe access rights 1.966
And I take note of which tps features are available 6.912
And I shutdown Tails and wait for the computer to power off 4.061
# 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.200
After features/support/hooks.rb:339 0.494
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.868
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 9.182
And I log in to a new session 11.171
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.806
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.386
Then the running Tails is installed on USB drive "to_upgrade" 18.802
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 1.595
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.189
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.101
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.781
Then all tps features from the old Tails version are active 1.095
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.313
And the expected persistent files created with the old Tails version are present in the filesystem 1.032
And all persistent directories from the old Tails version have safe access rights 1.652
After features/support/hooks.rb:339 0.502
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
3:46.780
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.364
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
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.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.331
When the network is plugged 0.030
And Tor is ready 12.011
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.549
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.952
Given I shutdown Tails and wait for the computer to power off 5.193
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.005
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.035
And the file system changes introduced in version 6.2~testoverlayfs are present 0.170
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.146
# 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.145
When the network is plugged 0.038
And Tor is ready 10.616
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.404
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.668
Given I shutdown Tails and wait for the computer to power off 4.256
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.936
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 11.414
And the file system changes introduced in version 6.3~testoverlayfs are present 0.239
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.032
And Tor is ready 10.159
Then the Upgrader considers the system as up-to-date 10.500
# 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.163
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.414
After features/support/hooks.rb:339 0.863
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
20.340
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.589
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.386
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 9.112
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.082
After features/support/hooks.rb:339 0.856
After features/support/hooks.rb:108 0.000