Project Number Date
test_Tails_ISO_stable-flatpak 19 16 Sep 2026, 19: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 10:57.952 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.768
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.177
When I start Tails from USB drive "old" with network unplugged 44.367
Then the boot device has safe access rights 1.591
And Tails is running from USB drive "old" 0.175
And there is no persistence partition on USB drive "old" 0.031
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.139
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 3.780
After features/support/hooks.rb:108 0.033
Tags: @product
1:23.597
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 48.810
Then Tails is running from USB drive "old" 0.210
And I create a persistent partition 24.118
And I take note of which tps features are available 5.974
Then a Tails persistence partition exists on USB drive "old" 0.416
And I shutdown Tails and wait for the computer to power off 3.995
After features/support/hooks.rb:339 0.239
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.387
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.915
Then Tails is running from USB drive "old" 0.248
And all tps features are active 7.265
When I write some files expected to persist 1.261
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.138
And all persistence configuration files have safe access rights 0.241
And all persistent directories from the old Tails version have safe access rights 1.639
And I take note of which tps features are available 5.861
And I shutdown Tails and wait for the computer to power off 2.595
# 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.131
After features/support/hooks.rb:339 0.418
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.632
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 7.985
And I log in to a new session 10.381
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.598
And I plug USB drive "to_upgrade" 2.373
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.584
Then the running Tails is installed on USB drive "to_upgrade" 17.472
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.118
After features/support/hooks.rb:339 1.694
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.726
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.725
Then all tps features from the old Tails version are active 1.143
And Tails is running from USB drive "to_upgrade" 0.206
And the boot device has safe access rights 2.369
And the expected persistent files created with the old Tails version are present in the filesystem 1.215
And all persistent directories from the old Tails version have safe access rights 1.993
After features/support/hooks.rb:339 0.924
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:27.088
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.997
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.350
When the network is plugged 0.024
And Tor is ready 12.173
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.129
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.648
Given I shutdown Tails and wait for the computer to power off 5.439
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.448
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.256
And the file system changes introduced in version 6.2~testoverlayfs are present 0.176
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.174
When the network is plugged 0.028
And Tor is ready 10.405
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.568
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.206
Given I shutdown Tails and wait for the computer to power off 2.559
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.806
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.839
And the file system changes introduced in version 6.3~testoverlayfs are present 0.299
And only the 6.3~testoverlayfs SquashFS delta is installed 0.032
# 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.074
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.147
When the network is plugged 0.028
And Tor is ready 10.403
Then the Upgrader considers the system as up-to-date 0.096
# 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.562
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.289
After features/support/hooks.rb:339 0.762
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
19.751
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.843
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
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.034
And Tor is ready 8.070
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.518
After features/support/hooks.rb:339 1.048
After features/support/hooks.rb:108 0.000