Project Number Date
test_Tails_ISO_stable 6677 17 Sep 2026, 11:41

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:22.659 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:9.352
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.100
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.382
When I start Tails from USB drive "old" with network unplugged 52.177
Then the boot device has safe access rights 2.078
And Tails is running from USB drive "old" 0.196
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 3.720
After features/support/hooks.rb:108 0.045
Tags: @product
1:21.850
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 46.930
Then Tails is running from USB drive "old" 0.216
And I create a persistent partition 22.976
And I take note of which tps features are available 6.042
Then a Tails persistence partition exists on USB drive "old" 0.511
And I shutdown Tails and wait for the computer to power off 5.085
After features/support/hooks.rb:339 0.458
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.653
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:0.250
Then Tails is running from USB drive "old" 0.200
And all tps features are active 7.182
When I write some files expected to persist 1.216
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.315
And all persistent directories from the old Tails version have safe access rights 1.580
And I take note of which tps features are available 5.578
And I shutdown Tails and wait for the computer to power off 2.518
# 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.502
After features/support/hooks.rb:339 0.153
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.516
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.159
And I log in to a new session 11.441
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.619
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.975
Then the running Tails is installed on USB drive "to_upgrade" 17.899
And I unplug USB drive "to_upgrade" 0.105
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 1.683
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.351
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.092
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.446
Then all tps features from the old Tails version are active 1.129
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 1.979
And the expected persistent files created with the old Tails version are present in the filesystem 0.972
And all persistent directories from the old Tails version have safe access rights 1.474
After features/support/hooks.rb:339 0.815
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
3:40.260
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.176
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
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.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.334
When the network is plugged 0.031
And Tor is ready 11.828
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.484
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.125
Given I shutdown Tails and wait for the computer to power off 5.427
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.257
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.086
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.101
# 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.189
When the network is plugged 0.032
And Tor is ready 10.304
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.869
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.680
Given I shutdown Tails and wait for the computer to power off 2.647
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.532
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.824
And the file system changes introduced in version 6.3~testoverlayfs are present 0.376
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.176
When the network is plugged 0.028
And Tor is ready 10.766
Then the Upgrader considers the system as up-to-date 10.398
# 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.118
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.339
After features/support/hooks.rb:339 0.582
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.674
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.736
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.030
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 9.560
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.070
After features/support/hooks.rb:339 0.999
After features/support/hooks.rb:108 0.000