Project Number Date
test_Tails_ISO_21565-flatpak-safe 134 10 Nov 2026, 03:24

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:53.599 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:12.637
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.412
When I start Tails from USB drive "old" with network unplugged 55.723
Then the boot device has safe access rights 1.855
And Tails is running from USB drive "old" 0.186
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.150
And I unplug USB drive "old" 0.107
After features/support/hooks.rb:339 3.358
After features/support/hooks.rb:108 0.071
Tags: @product
1:18.975
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 46.399
Then Tails is running from USB drive "old" 0.175
And I create a persistent partition 23.031
And I take note of which tps features are available 6.152
Then a Tails persistence partition exists on USB drive "old" 0.545
And I shutdown Tails and wait for the computer to power off 2.596
After features/support/hooks.rb:339 0.332
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.330
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.712
Then Tails is running from USB drive "old" 0.238
And all tps features are active 6.902
When I write some files expected to persist 0.978
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.260
And all persistent directories from the old Tails version have safe access rights 1.442
And I take note of which tps features are available 5.980
And I shutdown Tails and wait for the computer to power off 2.511
# 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.055
After features/support/hooks.rb:339 0.471
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.274
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.226
And I log in to a new session 11.277
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.650
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.762
Then the running Tails is installed on USB drive "to_upgrade" 17.887
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:339 1.663
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.111
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.645
Then all tps features from the old Tails version are active 0.945
And Tails is running from USB drive "to_upgrade" 0.194
And the boot device has safe access rights 1.964
And the expected persistent files created with the old Tails version are present in the filesystem 0.863
And all persistent directories from the old Tails version have safe access rights 1.426
After features/support/hooks.rb:339 0.504
After features/support/hooks.rb:108 0.014
3:21.763
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.047
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
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.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.315
When the network is plugged 0.035
And Tor is ready 13.223
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.287
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.315
Given I shutdown Tails and wait for the computer to power off 5.224
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.251
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.342
And the file system changes introduced in version 6.2~testoverlayfs are present 0.138
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.109
# 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.184
When the network is plugged 0.024
And Tor is ready 10.180
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.491
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.416
Given I shutdown Tails and wait for the computer to power off 3.919
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.099
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.255
And the file system changes introduced in version 6.3~testoverlayfs are present 0.317
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.102
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.206
When the network is plugged 0.043
And Tor is ready 10.101
Then the Upgrader considers the system as up-to-date 0.097
# 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.072
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.287
After features/support/hooks.rb:339 1.018
After features/support/hooks.rb:108 0.008
17.506
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.633
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 8.184
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.364
After features/support/hooks.rb:339 0.619
After features/support/hooks.rb:108 0.000