Project Number Date
test_Tails_ISO_stable-flatpak 43 11 Oct 2026, 19:49

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:12.344 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:1.058
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.017
When I start Tails from USB drive "old" with network unplugged 44.268
Then the boot device has safe access rights 2.028
And Tails is running from USB drive "old" 0.187
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.466
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.714
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 47.093
Then Tails is running from USB drive "old" 0.172
And I create a persistent partition 23.865
And I take note of which tps features are available 6.056
Then a Tails persistence partition exists on USB drive "old" 0.554
And I shutdown Tails and wait for the computer to power off 3.895
After features/support/hooks.rb:339 0.107
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.694
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.408
Then Tails is running from USB drive "old" 0.202
And all tps features are active 6.691
When I write some files expected to persist 1.202
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.143
And all persistence configuration files have safe access rights 0.222
And all persistent directories from the old Tails version have safe access rights 1.936
And I take note of which tps features are available 5.939
And I shutdown Tails and wait for the computer to power off 2.544
# 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.330
After features/support/hooks.rb:339 0.107
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.287
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.172
And I log in to a new session 11.667
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.947
And I plug USB drive "to_upgrade" 2.157
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.003
Then the running Tails is installed on USB drive "to_upgrade" 18.092
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.569
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.949
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.644
Then all tps features from the old Tails version are active 1.120
And Tails is running from USB drive "to_upgrade" 0.171
And the boot device has safe access rights 1.905
And the expected persistent files created with the old Tails version are present in the filesystem 0.955
And all persistent directories from the old Tails version have safe access rights 2.077
After features/support/hooks.rb:339 0.697
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:41.348
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 20.934
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.213
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.374
When the network is plugged 0.026
And Tor is ready 12.940
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.067
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.378
Given I shutdown Tails and wait for the computer to power off 5.244
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.081
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.572
And the file system changes introduced in version 6.2~testoverlayfs are present 0.225
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.122
# 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.174
When the network is plugged 0.028
And Tor is ready 11.148
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.906
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.027
Given I shutdown Tails and wait for the computer to power off 2.548
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.848
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 7.929
And the file system changes introduced in version 6.3~testoverlayfs are present 0.339
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.034
And Tor is ready 10.357
Then the Upgrader considers the system as up-to-date 0.111
# 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.655
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.300
After features/support/hooks.rb:339 0.933
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.291
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.676
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.040
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 8.181
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.121
After features/support/hooks.rb:339 1.005
After features/support/hooks.rb:108 0.000