Project Number Date
test_Tails_ISO_21565-flatpak-safe 53 27 Sep 2026, 03:39

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 10:55.719 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
59.666
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 12.881
When I start Tails from USB drive "old" with network unplugged 43.206
Then the boot device has safe access rights 1.940
And Tails is running from USB drive "old" 0.156
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.156
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 1.746
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.389
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 48.034
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 22.476
And I take note of which tps features are available 6.167
Then a Tails persistence partition exists on USB drive "old" 0.503
And I shutdown Tails and wait for the computer to power off 3.901
After features/support/hooks.rb:339 0.451
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.561
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 57.407
Then Tails is running from USB drive "old" 0.202
And all tps features are active 7.111
When I write some files expected to persist 0.936
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.139
And all persistence configuration files have safe access rights 0.300
And all persistent directories from the old Tails version have safe access rights 1.708
And I take note of which tps features are available 5.968
And I shutdown Tails and wait for the computer to power off 2.517
# 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.187
After features/support/hooks.rb:339 0.242
After features/support/hooks.rb:108 0.005
Tags: @product
2:8.622
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.195
And I log in to a new session 9.908
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.680
And I plug USB drive "to_upgrade" 2.197
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.410
Then the running Tails is installed on USB drive "to_upgrade" 16.976
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.517
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.988
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.813
Then all tps features from the old Tails version are active 0.975
And Tails is running from USB drive "to_upgrade" 0.206
And the boot device has safe access rights 1.949
And the expected persistent files created with the old Tails version are present in the filesystem 0.692
And all persistent directories from the old Tails version have safe access rights 1.278
After features/support/hooks.rb:339 0.685
After features/support/hooks.rb:108 0.005
3:22.017
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.986
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.025
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.195
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.261
When the network is plugged 0.035
And Tor is ready 12.819
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.878
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.232
Given I shutdown Tails and wait for the computer to power off 5.206
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.473
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.578
And the file system changes introduced in version 6.2~testoverlayfs are present 0.160
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.085
# 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.170
When the network is plugged 0.025
And Tor is ready 10.052
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.279
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.340
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 58.730
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 7.438
And the file system changes introduced in version 6.3~testoverlayfs are present 0.293
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.093
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.157
When the network is plugged 0.036
And Tor is ready 10.148
Then the Upgrader considers the system as up-to-date 0.079
# 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 2.934
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.317
After features/support/hooks.rb:339 0.843
After features/support/hooks.rb:108 0.009
32.473
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.541
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.029
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.040
And Tor is ready 10.787
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.815
After features/support/hooks.rb:339 0.666
After features/support/hooks.rb:108 0.000