Project Number Date
test_Tails_ISO_stable 6622 02 Sep 2026, 07:24

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:30.632 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:8.040
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.133
When I start Tails from USB drive "old" with network unplugged 51.461
Then the boot device has safe access rights 1.808
And Tails is running from USB drive "old" 0.166
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.029
And udev-watchdog is monitoring the correct device 0.153
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 1.544
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.252
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 48.369
Then Tails is running from USB drive "old" 0.226
And I create a persistent partition 23.113
And I take note of which tps features are available 6.406
Then a Tails persistence partition exists on USB drive "old" 0.513
And I shutdown Tails and wait for the computer to power off 2.549
After features/support/hooks.rb:339 0.646
After features/support/hooks.rb:108 0.009
Tags: @product
1:41.126
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.556
Then Tails is running from USB drive "old" 0.446
And all tps features are active 9.587
When I write some files expected to persist 0.999
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.118
And all persistence configuration files have safe access rights 0.296
And all persistent directories from the old Tails version have safe access rights 1.510
And I take note of which tps features are available 5.654
And I shutdown Tails and wait for the computer to power off 7.679
# 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.195
After features/support/hooks.rb:339 0.254
After features/support/hooks.rb:108 0.013
Tags: @product
2:14.261
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 8.847
And I log in to a new session 11.832
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.568
And I plug USB drive "to_upgrade" 2.343
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.549
Then the running Tails is installed on USB drive "to_upgrade" 18.894
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.110
After features/support/hooks.rb:339 3.845
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.401
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.750
Then all tps features from the old Tails version are active 1.069
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.319
And the expected persistent files created with the old Tails version are present in the filesystem 1.040
And all persistent directories from the old Tails version have safe access rights 1.877
After features/support/hooks.rb:339 0.774
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
3:39.638
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.162
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.217
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.310
When the network is plugged 0.030
And Tor is ready 12.277
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.206
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.862
Given I shutdown Tails and wait for the computer to power off 5.352
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.777
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.035
And the file system changes introduced in version 6.2~testoverlayfs are present 0.183
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.112
# 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.163
When the network is plugged 0.038
And Tor is ready 10.441
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.899
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.762
Given I shutdown Tails and wait for the computer to power off 2.644
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.514
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.348
And the file system changes introduced in version 6.3~testoverlayfs are present 0.322
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.110
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.027
And Tor is ready 10.488
Then the Upgrader considers the system as up-to-date 10.639
# 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.733
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.334
After features/support/hooks.rb:339 0.853
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
18.913
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.908
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
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.027
And Tor is ready 10.388
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.303
After features/support/hooks.rb:339 0.800
After features/support/hooks.rb:108 0.000