Project Number Date
test_Tails_ISO_21565-flatpak-safe 87 13 Oct 2026, 03: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:9.827 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:11.946
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.021
And I write an old version of the Tails USB image to disk "old" 13.531
When I start Tails from USB drive "old" with network unplugged 53.991
Then the boot device has safe access rights 2.663
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.169
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.653
After features/support/hooks.rb:108 0.043
Tags: @product
1:21.841
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 47.006
Then Tails is running from USB drive "old" 0.172
And I create a persistent partition 23.588
And I take note of which tps features are available 6.395
Then a Tails persistence partition exists on USB drive "old" 0.547
And I shutdown Tails and wait for the computer to power off 4.049
After features/support/hooks.rb:339 0.532
After features/support/hooks.rb:108 0.007
Tags: @product
1:32.525
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.889
Then Tails is running from USB drive "old" 0.303
And all tps features are active 7.274
When I write some files expected to persist 1.306
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.146
And all persistence configuration files have safe access rights 0.291
And all persistent directories from the old Tails version have safe access rights 1.558
And I take note of which tps features are available 6.324
And I shutdown Tails and wait for the computer to power off 2.525
# 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.804
After features/support/hooks.rb:339 0.301
After features/support/hooks.rb:108 0.013
Tags: @product
2:12.658
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.519
And I log in to a new session 11.326
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.769
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.927
Then the running Tails is installed on USB drive "to_upgrade" 18.656
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 0.576
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.680
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.833
Then all tps features from the old Tails version are active 1.151
And Tails is running from USB drive "to_upgrade" 0.183
And the boot device has safe access rights 2.363
And the expected persistent files created with the old Tails version are present in the filesystem 1.167
And all persistent directories from the old Tails version have safe access rights 1.891
After features/support/hooks.rb:339 0.537
After features/support/hooks.rb:108 0.020
3:22.760
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.010
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.335
When the network is plugged 0.031
And Tor is ready 13.215
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.320
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.548
Given I shutdown Tails and wait for the computer to power off 5.332
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.786
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.581
And the file system changes introduced in version 6.2~testoverlayfs are present 0.184
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.093
# 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.164
When the network is plugged 0.024
And Tor is ready 10.444
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.338
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.676
Given I shutdown Tails and wait for the computer to power off 2.603
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.830
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 6.550
And the file system changes introduced in version 6.3~testoverlayfs are present 0.311
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.120
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.379
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.611
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.317
After features/support/hooks.rb:339 0.649
After features/support/hooks.rb:108 0.045
18.413
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.720
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 9.872
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.308
After features/support/hooks.rb:339 0.713
After features/support/hooks.rb:108 0.000