Project Number Date
test_Tails_ISO_21565-flatpak-safe 110 29 Oct 2026, 03:40

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:46.954 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.897
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.130
When I start Tails from USB drive "old" with network unplugged 54.042
Then the boot device has safe access rights 2.080
And Tails is running from USB drive "old" 0.169
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.147
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.632
After features/support/hooks.rb:108 0.057
Tags: @product
1:16.632
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login 46.060
Then Tails is running from USB drive "old" 0.206
And I create a persistent partition 21.373
And I take note of which tps features are available 5.933
Then a Tails persistence partition exists on USB drive "old" 0.419
And I shutdown Tails and wait for the computer to power off 2.540
After features/support/hooks.rb:339 0.220
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.571
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.823
Then Tails is running from USB drive "old" 0.256
And all tps features are active 7.001
When I write some files expected to persist 1.136
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.107
And all persistence configuration files have safe access rights 0.259
And all persistent directories from the old Tails version have safe access rights 1.419
And I take note of which tps features are available 5.872
And I shutdown Tails and wait for the computer to power off 2.528
# 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.088
After features/support/hooks.rb:339 0.241
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.275
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.902
And I log in to a new session 11.203
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.658
And I plug USB drive "to_upgrade" 2.189
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.984
Then the running Tails is installed on USB drive "to_upgrade" 17.101
And I unplug USB drive "to_upgrade" 0.112
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.736
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.521
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.711
Then all tps features from the old Tails version are active 1.014
And Tails is running from USB drive "to_upgrade" 0.180
And the boot device has safe access rights 2.126
And the expected persistent files created with the old Tails version are present in the filesystem 0.895
And all persistent directories from the old Tails version have safe access rights 1.511
After features/support/hooks.rb:339 0.682
After features/support/hooks.rb:108 0.005
3:17.846
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.993
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.203
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.302
When the network is plugged 0.038
And Tor is ready 11.307
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.482
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.138
Given I shutdown Tails and wait for the computer to power off 5.469
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.968
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.455
And the file system changes introduced in version 6.2~testoverlayfs are present 0.260
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.175
When the network is plugged 0.028
And Tor is ready 10.215
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.299
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.330
Given I shutdown Tails and wait for the computer to power off 2.550
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.341
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 7.553
And the file system changes introduced in version 6.3~testoverlayfs are present 0.222
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.126
When the network is plugged 0.032
And Tor is ready 10.065
Then the Upgrader considers the system as up-to-date 0.075
# 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.199
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.265
After features/support/hooks.rb:339 0.997
After features/support/hooks.rb:108 0.009
17.209
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.654
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
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.030
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 7.673
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.586
After features/support/hooks.rb:339 0.931
After features/support/hooks.rb:108 0.000