Project Number Date
test_Tails_ISO_stable 6638 04 Sep 2026, 07:26

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:38.539 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:3.476
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.861
When I start Tails from USB drive "old" with network unplugged 45.913
Then the boot device has safe access rights 2.008
And Tails is running from USB drive "old" 0.194
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.027
And udev-watchdog is monitoring the correct device 0.156
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 3.582
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.913
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.105
And I start Tails from USB drive "old" with network unplugged and I login 49.013
Then Tails is running from USB drive "old" 0.275
And I create a persistent partition 23.525
And I take note of which tps features are available 6.318
Then a Tails persistence partition exists on USB drive "old" 0.597
And I shutdown Tails and wait for the computer to power off 4.077
After features/support/hooks.rb:339 0.463
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.153
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.138
Then Tails is running from USB drive "old" 0.248
And all tps features are active 8.256
When I write some files expected to persist 1.008
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.146
And all persistence configuration files have safe access rights 0.243
And all persistent directories from the old Tails version have safe access rights 1.489
And I take note of which tps features are available 6.749
And I shutdown Tails and wait for the computer to power off 4.203
# 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.584
After features/support/hooks.rb:339 0.127
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.068
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 9.099
And I log in to a new session 12.721
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.778
And I plug USB drive "to_upgrade" 2.276
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.637
Then the running Tails is installed on USB drive "to_upgrade" 18.291
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.116
After features/support/hooks.rb:339 1.482
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.995
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.601
Then all tps features from the old Tails version are active 1.028
And Tails is running from USB drive "to_upgrade" 0.202
And the boot device has safe access rights 2.144
And the expected persistent files created with the old Tails version are present in the filesystem 1.191
And all persistent directories from the old Tails version have safe access rights 1.748
After features/support/hooks.rb:339 0.949
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
3:56.171
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 22.428
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.175
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.359
When the network is plugged 0.026
And Tor is ready 13.502
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.917
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.324
Given I shutdown Tails and wait for the computer to power off 5.361
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.639
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.681
And the file system changes introduced in version 6.2~testoverlayfs are present 0.174
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.075
# 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.023
And Tor is ready 10.390
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.512
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.690
Given I shutdown Tails and wait for the computer to power off 3.956
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.314
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.733
And the file system changes introduced in version 6.3~testoverlayfs are present 0.321
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.081
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.234
When the network is plugged 0.031
And Tor is ready 10.346
Then the Upgrader considers the system as up-to-date 10.448
# 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.518
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.271
After features/support/hooks.rb:339 1.144
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
18.759
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.191
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
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.038
And Tor is ready 8.171
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.057
After features/support/hooks.rb:339 1.057
After features/support/hooks.rb:108 0.000