Project Number Date
test_Tails_ISO_stable 6720 04 Oct 2026, 11:36

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:35.856 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:17.124
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.540
When I start Tails from USB drive "old" with network unplugged 59.636
Then the boot device has safe access rights 2.207
And Tails is running from USB drive "old" 0.255
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.157
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.401
After features/support/hooks.rb:108 0.006
Tags: @product
1:23.238
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 47.743
Then Tails is running from USB drive "old" 0.197
And I create a persistent partition 24.277
And I take note of which tps features are available 6.472
Then a Tails persistence partition exists on USB drive "old" 0.494
And I shutdown Tails and wait for the computer to power off 3.974
After features/support/hooks.rb:339 0.617
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.290
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.619
Then Tails is running from USB drive "old" 0.199
And all tps features are active 8.104
When I write some files expected to persist 1.108
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.249
And all persistent directories from the old Tails version have safe access rights 1.682
And I take note of which tps features are available 5.807
And I shutdown Tails and wait for the computer to power off 2.503
# 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.759
After features/support/hooks.rb:339 0.510
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.029
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.399
And I log in to a new session 12.113
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.668
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.791
Then the running Tails is installed on USB drive "to_upgrade" 18.511
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.168
After features/support/hooks.rb:339 2.696
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.053
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.061
Then all tps features from the old Tails version are active 1.194
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 2.138
And the expected persistent files created with the old Tails version are present in the filesystem 0.889
And all persistent directories from the old Tails version have safe access rights 1.483
After features/support/hooks.rb:339 0.663
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
3:42.267
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.386
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.407
When the network is plugged 0.037
And Tor is ready 12.054
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.352
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.513
Given I shutdown Tails and wait for the computer to power off 5.721
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.885
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.913
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.035
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.202
When the network is plugged 0.033
And Tor is ready 10.265
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.322
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.108
Given I shutdown Tails and wait for the computer to power off 4.184
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.316
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.161
And the file system changes introduced in version 6.3~testoverlayfs are present 0.317
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.118
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.025
And Tor is ready 10.618
Then the Upgrader considers the system as up-to-date 10.439
# 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.244
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.317
After features/support/hooks.rb:339 0.597
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.852
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.987
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 10.240
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.287
After features/support/hooks.rb:339 0.801
After features/support/hooks.rb:108 0.000