Project Number Date
test_Tails_ISO_stable-flatpak 49 17 Oct 2026, 19:39

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:52.218 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:2.082
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.019
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 12.778
When I start Tails from USB drive "old" with network unplugged 45.562
Then the boot device has safe access rights 2.008
And Tails is running from USB drive "old" 0.213
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.174
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 3.468
After features/support/hooks.rb:108 0.044
Tags: @product
1:20.556
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 47.474
Then Tails is running from USB drive "old" 0.225
And I create a persistent partition 23.738
And I take note of which tps features are available 6.033
Then a Tails persistence partition exists on USB drive "old" 0.459
And I shutdown Tails and wait for the computer to power off 2.540
After features/support/hooks.rb:339 0.285
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.790
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.121
Then Tails is running from USB drive "old" 0.200
And all tps features are active 7.313
When I write some files expected to persist 1.313
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.133
And all persistence configuration files have safe access rights 0.262
And all persistent directories from the old Tails version have safe access rights 1.712
And I take note of which tps features are available 5.955
And I shutdown Tails and wait for the computer to power off 2.532
# 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.160
After features/support/hooks.rb:339 0.486
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.604
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.297
And I log in to a new session 11.242
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.622
And I plug USB drive "to_upgrade" 2.532
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.610
Then the running Tails is installed on USB drive "to_upgrade" 17.074
And I unplug USB drive "to_upgrade" 0.103
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.607
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.773
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.472
Then all tps features from the old Tails version are active 0.968
And Tails is running from USB drive "to_upgrade" 0.204
And the boot device has safe access rights 2.186
And the expected persistent files created with the old Tails version are present in the filesystem 1.000
And all persistent directories from the old Tails version have safe access rights 1.868
After features/support/hooks.rb:339 0.825
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:24.792
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.878
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.177
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.193
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.315
When the network is plugged 0.037
And Tor is ready 12.196
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.588
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.283
Given I shutdown Tails and wait for the computer to power off 5.192
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.003
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.788
And the file system changes introduced in version 6.2~testoverlayfs are present 0.156
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.111
# 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.172
When the network is plugged 0.034
And Tor is ready 10.047
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.921
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.100
Given I shutdown Tails and wait for the computer to power off 2.630
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.865
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 6.917
And the file system changes introduced in version 6.3~testoverlayfs are present 0.235
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.099
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186
When the network is plugged 0.025
And Tor is ready 10.444
Then the Upgrader considers the system as up-to-date 0.138
# 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.512
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.275
After features/support/hooks.rb:339 1.052
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.619
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.718
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.022
And the signing key used by the Upgrader is outdated 0.028
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 10.300
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.318
After features/support/hooks.rb:339 0.732
After features/support/hooks.rb:108 0.000