Project Number Date
test_Tails_ISO_stable-flatpak 29 27 Sep 2026, 20:11

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:29.968 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:16.113
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.036
When I start Tails from USB drive "old" with network unplugged 59.516
Then the boot device has safe access rights 1.835
And Tails is running from USB drive "old" 0.203
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.170
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 1.660
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.139
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.115
And I start Tails from USB drive "old" with network unplugged and I login 46.385
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 23.906
And I take note of which tps features are available 6.391
Then a Tails persistence partition exists on USB drive "old" 0.567
And I shutdown Tails and wait for the computer to power off 2.543
After features/support/hooks.rb:339 0.200
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.328
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.756
Then Tails is running from USB drive "old" 0.175
And all tps features are active 6.720
When I write some files expected to persist 1.220
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.210
And all persistent directories from the old Tails version have safe access rights 1.772
And I take note of which tps features are available 6.270
And I shutdown Tails and wait for the computer to power off 3.868
# 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.059
After features/support/hooks.rb:339 0.479
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.054
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.137
And I log in to a new session 11.372
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.669
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.856
Then the running Tails is installed on USB drive "to_upgrade" 16.586
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.107
After features/support/hooks.rb:339 1.651
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.662
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:1.469
Then all tps features from the old Tails version are active 1.108
And Tails is running from USB drive "to_upgrade" 0.204
And the boot device has safe access rights 1.896
And the expected persistent files created with the old Tails version are present in the filesystem 1.061
And all persistent directories from the old Tails version have safe access rights 1.842
After features/support/hooks.rb:339 0.622
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:38.329
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 8.058
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.179
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.310
When the network is plugged 0.037
And Tor is ready 13.605
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.154
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.451
Given I shutdown Tails and wait for the computer to power off 5.173
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.776
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.829
And the file system changes introduced in version 6.2~testoverlayfs are present 0.187
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.182
When the network is plugged 0.025
And Tor is ready 10.179
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 10.414
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.425
Given I shutdown Tails and wait for the computer to power off 3.769
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.537
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 7.863
And the file system changes introduced in version 6.3~testoverlayfs are present 0.324
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.083
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.167
When the network is plugged 0.030
And Tor is ready 10.850
Then the Upgrader considers the system as up-to-date 0.122
# 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.729
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.274
After features/support/hooks.rb:339 0.991
After features/support/hooks.rb:108 0.054
Tags: @product @automatic_upgrade
2:26.340
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.844
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 10.015
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2:8.139
After features/support/hooks.rb:339 0.846
After features/support/hooks.rb:108 0.000