Project Number Date
test_Tails_ISO_21548-flatpak-install 1 12 May 2026, 13:06

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 13:13.008 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:24.496
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.106
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.679
When I start Tails from USB drive "old" with network unplugged 1:4.274
Then the boot device has safe access rights 3.544
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:335 3.646
After features/support/hooks.rb:104 0.033
Tags: @product
1:32.559
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 57.388
Then Tails is running from USB drive "old" 0.246
And I create a persistent partition 26.137
And I take note of which tps features are available 0.855
Then a Tails persistence partition exists on USB drive "old" 0.595
And I shutdown Tails and wait for the computer to power off 7.246
After features/support/hooks.rb:335 0.300
After features/support/hooks.rb:104 0.008
Tags: @product
1:33.337
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.337
Then Tails is running from USB drive "old" 0.245
And all tps features are active 1.150
When I write some files expected to persist 1.389
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.513
And all persistent directories from the old Tails version have safe access rights 2.028
And I take note of which tps features are available 0.180
And I shutdown Tails and wait for the computer to power off 7.186
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.003
After features/support/hooks.rb:335 0.534
After features/support/hooks.rb:104 0.006
Tags: @product
2:15.115
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 without a persistent partition and stopped at Tails Greeter's login screen 9.178
And I log in to a new session 13.909
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.090
And I plug USB drive "to_upgrade" 2.309
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.077
Then the running Tails is installed on USB drive "to_upgrade" 16.237
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.170
After features/support/hooks.rb:335 2.153
After features/support/hooks.rb:104 0.000
Tags: @product
1:14.433
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.066
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.007
Then all tps features from the old Tails version are active 1.073
And Tails is running from USB drive "to_upgrade" 0.247
And the boot device has safe access rights 2.696
And the expected persistent files created with the old Tails version are present in the filesystem 1.293
And all persistent directories from the old Tails version have safe access rights 2.048
After features/support/hooks.rb:335 0.813
After features/support/hooks.rb:104 0.014
4:46.003
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 with a persistent partition enabled and logged in 8.780
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.384
When the network is plugged 0.017
And Tor is ready 20.652
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.398
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.553
Given I shutdown Tails and wait for the computer to power off 20.648
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.402
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.507
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.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.183
# 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.429
When the network is plugged 0.023
And Tor is ready 21.237
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.385
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.754
Given I shutdown Tails and wait for the computer to power off 14.385
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.818
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.100
And the file system changes introduced in version 6.3~testoverlayfs are present 0.360
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.163
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.018
And Tor is ready 21.948
Then the Upgrader considers the system as up-to-date 0.133
# 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 5.082
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 1.155
After features/support/hooks.rb:104 0.047
27.062
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.475
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 17.694
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.529
After features/support/hooks.rb:335 1.145
After features/support/hooks.rb:104 0.000