Project Number Date
test_Tails_ISO_21565-flatpak-safe 9 24 Aug 2026, 16:31

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:41.014 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:7.735
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 14.190
When I start Tails from USB drive "old" with network unplugged 49.544
Then the boot device has safe access rights 2.332
And Tails is running from USB drive "old" 0.196
And there is no persistence partition on USB drive "old" 0.026
And process "udev-watchdog" is running 0.034
And udev-watchdog is monitoring the correct device 0.150
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 4.034
After features/support/hooks.rb:108 0.006
Tags: @product
1:26.079
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login 50.045
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 23.804
And I take note of which tps features are available 7.192
Then a Tails persistence partition exists on USB drive "old" 0.620
And I shutdown Tails and wait for the computer to power off 4.055
After features/support/hooks.rb:339 0.293
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.440
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.741
Then Tails is running from USB drive "old" 0.218
And all tps features are active 7.528
When I write some files expected to persist 1.250
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.117
And all persistence configuration files have safe access rights 0.250
And all persistent directories from the old Tails version have safe access rights 1.646
And I take note of which tps features are available 6.220
And I shutdown Tails and wait for the computer to power off 2.533
# 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.836
After features/support/hooks.rb:339 0.425
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.980
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.364
And I log in to a new session 12.012
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.637
And I plug USB drive "to_upgrade" 2.181
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.860
Then the running Tails is installed on USB drive "to_upgrade" 18.630
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:339 4.400
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.370
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 2.155
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.914
Then all tps features from the old Tails version are active 1.318
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.487
And the expected persistent files created with the old Tails version are present in the filesystem 1.542
And all persistent directories from the old Tails version have safe access rights 1.694
After features/support/hooks.rb:339 1.214
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:41.911
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 9.256
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.183
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.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.260
When the network is plugged 0.044
And Tor is ready 12.061
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.289
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.106
Given I shutdown Tails and wait for the computer to power off 5.308
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.986
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 8.268
And the file system changes introduced in version 6.2~testoverlayfs are present 0.159
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.099
# 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.208
When the network is plugged 0.025
And Tor is ready 10.571
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.948
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.805
Given I shutdown Tails and wait for the computer to power off 2.691
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.719
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.774
And the file system changes introduced in version 6.3~testoverlayfs are present 0.445
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.103
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.172
When the network is plugged 0.026
And Tor is ready 10.532
Then the Upgrader considers the system as up-to-date 10.439
# 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.662
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.333
After features/support/hooks.rb:339 1.040
After features/support/hooks.rb:108 0.046
Tags: @product @automatic_upgrade
20.496
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.538
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 9.980
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.587
After features/support/hooks.rb:339 0.683
After features/support/hooks.rb:108 0.000