Project Number Date
test_Tails_ISO_21565-flatpak-safe 105 27 Oct 2026, 20:12

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:16.797 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:4.135
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.034
And I write an old version of the Tails USB image to disk "old" 13.340
When I start Tails from USB drive "old" with network unplugged 46.777
Then the boot device has safe access rights 2.302
And Tails is running from USB drive "old" 0.194
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.157
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 1.181
After features/support/hooks.rb:108 0.005
Tags: @product
1:22.614
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 49.010
Then Tails is running from USB drive "old" 0.177
And I create a persistent partition 23.487
And I take note of which tps features are available 6.750
Then a Tails persistence partition exists on USB drive "old" 0.508
And I shutdown Tails and wait for the computer to power off 2.602
After features/support/hooks.rb:339 0.262
After features/support/hooks.rb:108 0.007
Tags: @product
1:35.582
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.694
Then Tails is running from USB drive "old" 0.198
And all tps features are active 8.900
When I write some files expected to persist 1.177
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.123
And all persistence configuration files have safe access rights 0.238
And all persistent directories from the old Tails version have safe access rights 1.572
And I take note of which tps features are available 6.148
And I shutdown Tails and wait for the computer to power off 2.577
# 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.862
After features/support/hooks.rb:339 0.221
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.246
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.470
And I log in to a new session 12.703
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.638
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.694
Then the running Tails is installed on USB drive "to_upgrade" 17.301
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.118
After features/support/hooks.rb:339 2.137
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.024
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.821
Then all tps features from the old Tails version are active 1.029
And Tails is running from USB drive "to_upgrade" 0.208
And the boot device has safe access rights 2.160
And the expected persistent files created with the old Tails version are present in the filesystem 1.012
And all persistent directories from the old Tails version have safe access rights 1.698
After features/support/hooks.rb:339 0.709
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
3:32.538
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 with a persistent partition enabled and logged in 8.426
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.216
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.268
When the network is plugged 0.026
And Tor is ready 11.940
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.856
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.914
Given I shutdown Tails and wait for the computer to power off 5.447
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.209
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.877
And the file system changes introduced in version 6.2~testoverlayfs are present 0.186
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.124
# 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.192
When the network is plugged 0.026
And Tor is ready 10.726
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.328
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.557
Given I shutdown Tails and wait for the computer to power off 4.232
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.001
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.006
And the file system changes introduced in version 6.3~testoverlayfs are present 0.410
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.116
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.026
And Tor is ready 9.715
Then the Upgrader considers the system as up-to-date 0.091
# 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.522
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.404
After features/support/hooks.rb:339 0.813
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
17.654
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.740
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 8.536
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.001
After features/support/hooks.rb:339 0.492
After features/support/hooks.rb:108 0.000