Project Number Date
test_Tails_ISO_stable 6621 01 Sep 2026, 22:57

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:37.210 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:4.166
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.108
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 14.075
When I start Tails from USB drive "old" with network unplugged 45.831
Then the boot device has safe access rights 2.454
And Tails is running from USB drive "old" 0.201
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 1.505
After features/support/hooks.rb:108 0.022
Tags: @product
1:25.719
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login 51.320
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 23.578
And I take note of which tps features are available 7.217
Then a Tails persistence partition exists on USB drive "old" 0.603
And I shutdown Tails and wait for the computer to power off 2.657
After features/support/hooks.rb:339 0.177
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.798
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 "old" with network unplugged and I login with persistence enabled 1:4.444
Then Tails is running from USB drive "old" 0.208
And all tps features are active 7.377
When I write some files expected to persist 1.125
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 2.520
And I take note of which tps features are available 7.545
And I shutdown Tails and wait for the computer to power off 2.624
# 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.377
After features/support/hooks.rb:339 0.474
After features/support/hooks.rb:108 0.005
Tags: @product
2:16.875
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.720
And I log in to a new session 13.065
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.898
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.491
Then the running Tails is installed on USB drive "to_upgrade" 19.234
And I unplug USB drive "to_upgrade" 0.111
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 3.754
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.070
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.102
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.981
Then all tps features from the old Tails version are active 1.115
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.464
And the expected persistent files created with the old Tails version are present in the filesystem 1.188
And all persistent directories from the old Tails version have safe access rights 1.964
After features/support/hooks.rb:339 0.735
After features/support/hooks.rb:108 0.056
Tags: @product @automatic_upgrade
3:38.387
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.033
And no SquashFS delta is installed 0.088
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.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.042
And Tor is ready 12.324
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.216
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.578
Given I shutdown Tails and wait for the computer to power off 5.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.638
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.750
And the file system changes introduced in version 6.2~testoverlayfs are present 0.259
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.107
# 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.194
When the network is plugged 0.036
And Tor is ready 10.721
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.036
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.109
Given I shutdown Tails and wait for the computer to power off 3.917
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.765
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.789
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
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.111
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.168
When the network is plugged 0.027
And Tor is ready 10.547
Then the Upgrader considers the system as up-to-date 0.096
# 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.695
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.354
After features/support/hooks.rb:339 0.947
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.192
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.558
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 10.109
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.138
After features/support/hooks.rb:339 1.283
After features/support/hooks.rb:108 0.000