Project Number Date
test_Tails_ISO_21565-flatpak-safe 44 22 Sep 2026, 13:56

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:22.143 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:17.474
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.185
When I start Tails from USB drive "old" with network unplugged 1:0.163
Then the boot device has safe access rights 2.408
And Tails is running from USB drive "old" 0.191
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.033
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.112
After features/support/hooks.rb:339 1.243
After features/support/hooks.rb:108 0.016
Tags: @product
1:23.611
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 48.057
Then Tails is running from USB drive "old" 0.195
And I create a persistent partition 23.816
And I take note of which tps features are available 6.721
Then a Tails persistence partition exists on USB drive "old" 0.577
And I shutdown Tails and wait for the computer to power off 4.138
After features/support/hooks.rb:339 0.222
After features/support/hooks.rb:108 0.005
Tags: @product
1:33.646
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.254
Then Tails is running from USB drive "old" 0.211
And all tps features are active 7.099
When I write some files expected to persist 0.999
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.207
And all persistent directories from the old Tails version have safe access rights 1.717
And I take note of which tps features are available 6.367
And I shutdown Tails and wait for the computer to power off 3.911
# 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.619
After features/support/hooks.rb:339 0.191
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.334
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.500
And I log in to a new session 11.829
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.645
And I plug USB drive "to_upgrade" 2.553
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.347
Then the running Tails is installed on USB drive "to_upgrade" 17.241
And I unplug USB drive "to_upgrade" 0.109
And I unplug USB drive "__internal" 0.107
After features/support/hooks.rb:339 1.785
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.811
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.340
Then all tps features from the old Tails version are active 0.919
And Tails is running from USB drive "to_upgrade" 0.199
And the boot device has safe access rights 1.926
And the expected persistent files created with the old Tails version are present in the filesystem 0.902
And all persistent directories from the old Tails version have safe access rights 1.444
After features/support/hooks.rb:339 0.823
After features/support/hooks.rb:108 0.005
3:31.823
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.017
And no SquashFS delta is installed 0.081
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.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.137
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.263
When the network is plugged 0.033
And Tor is ready 11.231
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.139
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.564
Given I shutdown Tails and wait for the computer to power off 5.210
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.866
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.456
And the file system changes introduced in version 6.2~testoverlayfs are present 0.165
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.151
When the network is plugged 0.034
And Tor is ready 10.096
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.874
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.432
Given I shutdown Tails and wait for the computer to power off 4.069
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.675
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.489
And the file system changes introduced in version 6.3~testoverlayfs are present 0.329
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.090
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.036
And Tor is ready 10.099
Then the Upgrader considers the system as up-to-date 10.354
# 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 2.989
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.272
After features/support/hooks.rb:339 1.007
After features/support/hooks.rb:108 0.049
18.442
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.731
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.187
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 8.016
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.372
After features/support/hooks.rb:339 0.711
After features/support/hooks.rb:108 0.000