Project Number Date
test_Tails_ISO_stable-flatpak 36 04 Oct 2026, 19:43

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:12.009 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:13.527
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.313
When I start Tails from USB drive "old" with network unplugged 56.613
Then the boot device has safe access rights 1.950
And Tails is running from USB drive "old" 0.170
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.028
And udev-watchdog is monitoring the correct device 0.166
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 3.549
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.828
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 46.370
Then Tails is running from USB drive "old" 0.194
And I create a persistent partition 23.460
And I take note of which tps features are available 6.044
Then a Tails persistence partition exists on USB drive "old" 0.539
And I shutdown Tails and wait for the computer to power off 5.148
After features/support/hooks.rb:339 0.540
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.450
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 with persistence enabled 59.672
Then Tails is running from USB drive "old" 0.174
And all tps features are active 7.205
When I write some files expected to persist 1.234
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
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.933
And I take note of which tps features are available 5.894
And I shutdown Tails and wait for the computer to power off 2.508
# 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.299
After features/support/hooks.rb:339 0.354
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.202
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.027
And I log in to a new session 10.955
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.598
And I plug USB drive "to_upgrade" 2.240
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.203
Then the running Tails is installed on USB drive "to_upgrade" 16.931
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 0.559
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.331
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.110
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.757
Then all tps features from the old Tails version are active 0.985
And Tails is running from USB drive "to_upgrade" 0.192
And the boot device has safe access rights 2.245
And the expected persistent files created with the old Tails version are present in the filesystem 1.056
And all persistent directories from the old Tails version have safe access rights 1.982
After features/support/hooks.rb:339 0.816
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
3:29.166
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.022
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.210
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.287
When the network is plugged 0.025
And Tor is ready 13.865
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.957
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.195
Given I shutdown Tails and wait for the computer to power off 6.485
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.401
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.652
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.103
# 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.161
When the network is plugged 0.035
And Tor is ready 10.424
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.069
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.175
Given I shutdown Tails and wait for the computer to power off 3.983
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.643
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.241
And the file system changes introduced in version 6.3~testoverlayfs are present 0.256
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.162
When the network is plugged 0.035
And Tor is ready 10.424
Then the Upgrader considers the system as up-to-date 0.128
# 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.117
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.284
After features/support/hooks.rb:339 0.631
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.501
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.636
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 11.215
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.314
After features/support/hooks.rb:339 0.842
After features/support/hooks.rb:108 0.000