Project Number Date
test_Tails_ISO_21565-flatpak-safe 39 18 Sep 2026, 03:22

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.498 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:19.331
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.178
When I start Tails from USB drive "old" with network unplugged 1:2.652
Then the boot device has safe access rights 1.900
And Tails is running from USB drive "old" 0.149
And there is no persistence partition on USB drive "old" 0.031
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.153
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 1.902
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.917
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 47.899
Then Tails is running from USB drive "old" 0.217
And I create a persistent partition 22.054
And I take note of which tps features are available 6.089
Then a Tails persistence partition exists on USB drive "old" 0.609
And I shutdown Tails and wait for the computer to power off 3.957
After features/support/hooks.rb:339 0.372
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.550
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.702
Then Tails is running from USB drive "old" 0.180
And all tps features are active 7.059
When I write some files expected to persist 1.167
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.101
And all persistence configuration files have safe access rights 0.332
And all persistent directories from the old Tails version have safe access rights 1.443
And I take note of which tps features are available 5.668
And I shutdown Tails and wait for the computer to power off 2.554
# 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.257
After features/support/hooks.rb:339 0.250
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.207
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.415
And I log in to a new session 11.033
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.602
And I plug USB drive "to_upgrade" 2.665
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.349
Then the running Tails is installed on USB drive "to_upgrade" 17.875
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 1.644
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.876
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.191
Then all tps features from the old Tails version are active 0.994
And Tails is running from USB drive "to_upgrade" 0.210
And the boot device has safe access rights 1.959
And the expected persistent files created with the old Tails version are present in the filesystem 0.954
And all persistent directories from the old Tails version have safe access rights 1.492
After features/support/hooks.rb:339 0.748
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:22.560
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.968
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.350
When the network is plugged 0.040
And Tor is ready 13.215
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.863
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.727
Given I shutdown Tails and wait for the computer to power off 5.360
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.834
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.053
And the file system changes introduced in version 6.2~testoverlayfs are present 0.166
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.100
# 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.151
When the network is plugged 0.034
And Tor is ready 10.119
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.479
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.403
Given I shutdown Tails and wait for the computer to power off 2.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.310
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.026
And the file system changes introduced in version 6.3~testoverlayfs are present 0.326
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.115
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.150
When the network is plugged 0.032
And Tor is ready 10.097
Then the Upgrader considers the system as up-to-date 0.096
# 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.996
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.321
After features/support/hooks.rb:339 0.848
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.053
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.817
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.044
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 8.028
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.877
After features/support/hooks.rb:339 0.591
After features/support/hooks.rb:108 0.000