Project Number Date
test_Tails_ISO_21565-flatpak-safe 113 31 Oct 2026, 03:37

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:2.909 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.992
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.903
When I start Tails from USB drive "old" with network unplugged 57.905
Then the boot device has safe access rights 1.593
And Tails is running from USB drive "old" 0.144
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.135
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.536
After features/support/hooks.rb:108 0.068
Tags: @product
1:18.264
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 "old" with network unplugged and I login 46.529
Then Tails is running from USB drive "old" 0.197
And I create a persistent partition 22.512
And I take note of which tps features are available 5.944
Then a Tails persistence partition exists on USB drive "old" 0.469
And I shutdown Tails and wait for the computer to power off 2.532
After features/support/hooks.rb:339 0.591
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.215
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.372
Then Tails is running from USB drive "old" 0.235
And all tps features are active 6.883
When I write some files expected to persist 1.038
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.116
And all persistence configuration files have safe access rights 0.254
And all persistent directories from the old Tails version have safe access rights 1.463
And I take note of which tps features are available 5.917
And I shutdown Tails and wait for the computer to power off 2.498
# 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.332
After features/support/hooks.rb:339 0.147
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.176
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.204
And I log in to a new session 10.972
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.608
And I plug USB drive "to_upgrade" 2.266
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.139
Then the running Tails is installed on USB drive "to_upgrade" 17.757
And I unplug USB drive "to_upgrade" 0.108
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.559
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.868
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.367
Then all tps features from the old Tails version are active 1.086
And Tails is running from USB drive "to_upgrade" 0.138
And the boot device has safe access rights 1.776
And the expected persistent files created with the old Tails version are present in the filesystem 0.934
And all persistent directories from the old Tails version have safe access rights 1.485
After features/support/hooks.rb:339 0.750
After features/support/hooks.rb:108 0.039
3:29.926
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 21.066
And no SquashFS delta is installed 0.044
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.032
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.157
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.232
When the network is plugged 0.024
And Tor is ready 12.789
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.312
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.385
Given I shutdown Tails and wait for the computer to power off 5.156
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.370
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 6.928
And the file system changes introduced in version 6.2~testoverlayfs are present 0.180
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.094
# 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.131
When the network is plugged 0.031
And Tor is ready 10.339
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.841
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.564
Given I shutdown Tails and wait for the computer to power off 2.584
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.073
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.266
And the file system changes introduced in version 6.3~testoverlayfs are present 0.288
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.094
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.176
When the network is plugged 0.031
And Tor is ready 9.920
Then the Upgrader considers the system as up-to-date 0.098
# 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.080
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.347
After features/support/hooks.rb:339 0.817
After features/support/hooks.rb:108 0.009
18.466
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.735
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
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.032
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 7.895
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.513
After features/support/hooks.rb:339 0.671
After features/support/hooks.rb:108 0.000