Project Number Date
test_Tails_ISO_21565-flatpak-safe 3 20 Aug 2026, 03:16

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.232 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:13.506
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 13.154
When I start Tails from USB drive "old" with network unplugged 56.741
Then the boot device has safe access rights 1.927
And Tails is running from USB drive "old" 0.200
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.158
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 3.560
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.856
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 46.583
Then Tails is running from USB drive "old" 0.180
And I create a persistent partition 22.927
And I take note of which tps features are available 6.095
Then a Tails persistence partition exists on USB drive "old" 0.459
And I shutdown Tails and wait for the computer to power off 2.532
After features/support/hooks.rb:339 0.466
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.827
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.240
Then Tails is running from USB drive "old" 0.181
And all tps features are active 6.410
When I write some files expected to persist 0.923
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.331
And all persistent directories from the old Tails version have safe access rights 1.604
And I take note of which tps features are available 6.017
And I shutdown Tails and wait for the computer to power off 2.552
# 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.280
After features/support/hooks.rb:339 0.509
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.674
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.441
And I log in to a new session 11.408
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.589
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.613
Then the running Tails is installed on USB drive "to_upgrade" 18.147
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 6.742
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.260
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.972
Then all tps features from the old Tails version are active 1.219
And Tails is running from USB drive "to_upgrade" 0.162
And the boot device has safe access rights 2.288
And the expected persistent files created with the old Tails version are present in the filesystem 0.939
And all persistent directories from the old Tails version have safe access rights 1.595
After features/support/hooks.rb:339 0.898
After features/support/hooks.rb:108 0.005
3:31.145
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.932
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.183
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.314
When the network is plugged 0.034
And Tor is ready 11.903
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.547
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.701
Given I shutdown Tails and wait for the computer to power off 5.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.469
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 6.945
And the file system changes introduced in version 6.2~testoverlayfs are present 0.170
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.099
# 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.149
When the network is plugged 0.033
And Tor is ready 9.945
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.599
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.547
Given I shutdown Tails and wait for the computer to power off 2.551
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.712
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.195
And the file system changes introduced in version 6.3~testoverlayfs are present 0.257
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.149
When the network is plugged 0.034
And Tor is ready 10.150
Then the Upgrader considers the system as up-to-date 10.423
# 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.049
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.250
After features/support/hooks.rb:339 0.692
After features/support/hooks.rb:108 0.009
17.962
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.870
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.183
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 7.808
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.961
After features/support/hooks.rb:339 0.713
After features/support/hooks.rb:108 0.000