Project Number Date
test_Tails_ISO_stable-flatpak 44 12 Oct 2026, 19:51

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:15.699 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:10.510
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.101
When I start Tails from USB drive "old" with network unplugged 53.844
Then the boot device has safe access rights 1.843
And Tails is running from USB drive "old" 0.201
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.035
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:339 3.527
After features/support/hooks.rb:108 0.052
Tags: @product
1:22.371
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 48.622
Then Tails is running from USB drive "old" 0.189
And I create a persistent partition 22.963
And I take note of which tps features are available 5.914
Then a Tails persistence partition exists on USB drive "old" 0.481
And I shutdown Tails and wait for the computer to power off 4.123
After features/support/hooks.rb:339 0.465
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.764
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.520
Then Tails is running from USB drive "old" 0.213
And all tps features are active 6.796
When I write some files expected to persist 1.180
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.102
And all persistence configuration files have safe access rights 0.255
And all persistent directories from the old Tails version have safe access rights 1.711
And I take note of which tps features are available 5.810
And I shutdown Tails and wait for the computer to power off 4.055
# 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.028
After features/support/hooks.rb:339 0.509
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.080
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.266
And I log in to a new session 10.255
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.630
And I plug USB drive "to_upgrade" 2.732
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.327
Then the running Tails is installed on USB drive "to_upgrade" 17.600
And I unplug USB drive "to_upgrade" 0.151
And I unplug USB drive "__internal" 0.116
After features/support/hooks.rb:339 1.636
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.884
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.822
Then all tps features from the old Tails version are active 1.151
And Tails is running from USB drive "to_upgrade" 0.204
And the boot device has safe access rights 1.882
And the expected persistent files created with the old Tails version are present in the filesystem 1.084
And all persistent directories from the old Tails version have safe access rights 1.666
After features/support/hooks.rb:339 0.760
After features/support/hooks.rb:108 0.005
3:35.888
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.145
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.170
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.182
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.037
And Tor is ready 11.393
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.790
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.192
Given I shutdown Tails and wait for the computer to power off 5.265
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.967
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 7.204
And the file system changes introduced in version 6.2~testoverlayfs are present 0.196
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.115
# 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.141
When the network is plugged 0.023
And Tor is ready 10.242
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.521
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.580
Given I shutdown Tails and wait for the computer to power off 3.965
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.127
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.398
And the file system changes introduced in version 6.3~testoverlayfs are present 0.285
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.120
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.176
When the network is plugged 0.026
And Tor is ready 10.078
Then the Upgrader considers the system as up-to-date 10.468
# 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.114
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.389
After features/support/hooks.rb:339 0.937
After features/support/hooks.rb:108 0.037
20.198
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.664
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 9.749
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.451
After features/support/hooks.rb:339 1.015
After features/support/hooks.rb:108 0.000