Project Number Date
test_Tails_ISO_stable-flatpak 50 18 Oct 2026, 19:56

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:7.940 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:0.040
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 12.771
When I start Tails from USB drive "old" with network unplugged 43.673
Then the boot device has safe access rights 1.875
And Tails is running from USB drive "old" 0.173
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 3.488
After features/support/hooks.rb:108 0.052
Tags: @product
1:22.515
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 48.091
Then Tails is running from USB drive "old" 0.235
And I create a persistent partition 23.486
And I take note of which tps features are available 6.269
Then a Tails persistence partition exists on USB drive "old" 0.421
And I shutdown Tails and wait for the computer to power off 3.927
After features/support/hooks.rb:339 0.317
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.389
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.758
Then Tails is running from USB drive "old" 0.210
And all tps features are active 6.779
When I write some files expected to persist 1.215
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.115
And all persistence configuration files have safe access rights 0.248
And all persistent directories from the old Tails version have safe access rights 2.010
And I take note of which tps features are available 6.192
And I shutdown Tails and wait for the computer to power off 2.558
# 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.209
After features/support/hooks.rb:339 0.413
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.595
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.301
And I log in to a new session 11.056
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.679
And I plug USB drive "to_upgrade" 2.198
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.413
Then the running Tails is installed on USB drive "to_upgrade" 16.719
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.683
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.679
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.565
Then all tps features from the old Tails version are active 1.082
And Tails is running from USB drive "to_upgrade" 0.198
And the boot device has safe access rights 1.791
And the expected persistent files created with the old Tails version are present in the filesystem 1.062
And all persistent directories from the old Tails version have safe access rights 1.899
After features/support/hooks.rb:339 0.492
After features/support/hooks.rb:108 0.053
Tags: @product @automatic_upgrade
3:39.383
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.061
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.196
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.263
When the network is plugged 0.034
And Tor is ready 11.788
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.999
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.325
Given I shutdown Tails and wait for the computer to power off 5.295
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.807
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.820
And the file system changes introduced in version 6.2~testoverlayfs are present 0.168
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.102
# 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.157
When the network is plugged 0.032
And Tor is ready 10.088
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.101
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.746
Given I shutdown Tails and wait for the computer to power off 5.203
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.823
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.267
And the file system changes introduced in version 6.3~testoverlayfs are present 0.329
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.145
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.153
When the network is plugged 0.036
And Tor is ready 10.179
Then the Upgrader considers the system as up-to-date 10.396
# 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.033
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.401
After features/support/hooks.rb:339 0.949
After features/support/hooks.rb:108 0.058
Tags: @product @automatic_upgrade
19.336
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.720
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.178
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 9.601
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.730
After features/support/hooks.rb:339 1.022
After features/support/hooks.rb:108 0.000