Project Number Date
test_Tails_ISO_21548-flatpak-install 3 13 May 2026, 14:19

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:58.186 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:0.990
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 12.450
When I start Tails from USB drive "old" with network unplugged 44.010
Then the boot device has safe access rights 2.782
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:335 3.569
After features/support/hooks.rb:104 0.013
Tags: @product
1:23.747
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 51.137
Then Tails is running from USB drive "old" 0.245
And I create a persistent partition 23.579
And I take note of which tps features are available 0.326
Then a Tails persistence partition exists on USB drive "old" 0.520
And I shutdown Tails and wait for the computer to power off 7.890
After features/support/hooks.rb:335 0.583
After features/support/hooks.rb:104 0.007
Tags: @product
1:23.536
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.168
Then Tails is running from USB drive "old" 0.211
And all tps features are active 1.025
When I write some files expected to persist 1.200
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
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.746
And I take note of which tps features are available 0.183
And I shutdown Tails and wait for the computer to power off 7.920
# 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.569
After features/support/hooks.rb:335 0.303
After features/support/hooks.rb:104 0.008
Tags: @product
2:8.117
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.214
And I log in to a new session 11.101
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.709
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.115
Then the running Tails is installed on USB drive "to_upgrade" 15.473
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:335 2.195
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.704
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.129
Then all tps features from the old Tails version are active 1.014
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.510
And the expected persistent files created with the old Tails version are present in the filesystem 1.073
And all persistent directories from the old Tails version have safe access rights 1.701
After features/support/hooks.rb:335 0.500
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:35.515
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 8.012
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
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.233
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.332
When the network is plugged 0.018
And Tor is ready 13.674
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.027
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.624
Given I shutdown Tails and wait for the computer to power off 9.454
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.529
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.042
And the file system changes introduced in version 6.2~testoverlayfs are present 0.225
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.196
# 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.015
And Tor is ready 9.813
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.028
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.010
Given I shutdown Tails and wait for the computer to power off 8.112
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.341
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.345
And the file system changes introduced in version 6.3~testoverlayfs are present 0.384
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.189
When the network is plugged 0.014
And Tor is ready 10.038
Then the Upgrader considers the system as up-to-date 10.579
# 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.146
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.325
After features/support/hooks.rb:335 0.930
After features/support/hooks.rb:104 0.026
Tags: @product @automatic_upgrade
19.574
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.139
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.035
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 11.085
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.043
After features/support/hooks.rb:335 0.651
After features/support/hooks.rb:104 0.000