Project Number Date
test_Tails_ISO_21548-flatpak-install 5 15 May 2026, 14:25

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:34.813 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:9.134
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.622
When I start Tails from USB drive "old" with network unplugged 50.519
Then the boot device has safe access rights 3.023
And Tails is running from USB drive "old" 0.361
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.266
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:335 1.698
After features/support/hooks.rb:104 0.036
Tags: @product
1:25.863
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 55.440
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 24.946
And I take note of which tps features are available 0.363
Then a Tails persistence partition exists on USB drive "old" 0.590
And I shutdown Tails and wait for the computer to power off 4.210
After features/support/hooks.rb:335 0.486
After features/support/hooks.rb:104 0.006
Tags: @product
1:28.061
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.159
Then Tails is running from USB drive "old" 0.232
And all tps features are active 1.137
When I write some files expected to persist 1.344
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.324
And all persistent directories from the old Tails version have safe access rights 2.024
And I take note of which tps features are available 0.200
And I shutdown Tails and wait for the computer to power off 7.063
# 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" 12.359
After features/support/hooks.rb:335 0.304
After features/support/hooks.rb:104 0.012
Tags: @product
2:13.637
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.101
And I log in to a new session 13.008
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.206
And I plug USB drive "to_upgrade" 2.327
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.105
Then the running Tails is installed on USB drive "to_upgrade" 16.594
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:335 0.711
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.987
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.023
Then all tps features from the old Tails version are active 1.138
And Tails is running from USB drive "to_upgrade" 0.248
And the boot device has safe access rights 2.677
And the expected persistent files created with the old Tails version are present in the filesystem 1.425
And all persistent directories from the old Tails version have safe access rights 2.409
After features/support/hooks.rb:335 0.718
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
3:46.739
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.536
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.202
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.364
When the network is plugged 0.016
And Tor is ready 12.810
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.735
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.757
Given I shutdown Tails and wait for the computer to power off 9.376
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.492
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.166
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.199
When the network is plugged 0.018
And Tor is ready 11.768
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.132
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.739
Given I shutdown Tails and wait for the computer to power off 7.992
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.019
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.168
And the file system changes introduced in version 6.3~testoverlayfs are present 0.562
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.017
And Tor is ready 11.703
Then the Upgrader considers the system as up-to-date 10.576
# 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 4.696
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.439
After features/support/hooks.rb:335 0.643
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
20.389
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.274
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.402
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.332
After features/support/hooks.rb:335 0.788
After features/support/hooks.rb:104 0.000