Project Number Date
test_Tails_ISO_stable-flatpak 51 19 Oct 2026, 19:37

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:4.529 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:5.119
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.103
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.169
When I start Tails from USB drive "old" with network unplugged 48.259
Then the boot device has safe access rights 1.892
And Tails is running from USB drive "old" 0.281
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 3.423
After features/support/hooks.rb:108 0.028
Tags: @product
1:21.756
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 47.182
Then Tails is running from USB drive "old" 0.208
And I create a persistent partition 23.320
And I take note of which tps features are available 6.413
Then a Tails persistence partition exists on USB drive "old" 0.617
And I shutdown Tails and wait for the computer to power off 3.923
After features/support/hooks.rb:339 0.538
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.636
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.837
Then Tails is running from USB drive "old" 0.184
And all tps features are active 7.007
When I write some files expected to persist 1.198
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.130
And all persistence configuration files have safe access rights 0.287
And all persistent directories from the old Tails version have safe access rights 1.809
And I take note of which tps features are available 5.885
And I shutdown Tails and wait for the computer to power off 5.223
# 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" 10.975
After features/support/hooks.rb:339 0.171
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.673
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.404
And I log in to a new session 11.451
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.632
And I plug USB drive "to_upgrade" 2.197
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.013
Then the running Tails is installed on USB drive "to_upgrade" 17.738
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 1.743
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.750
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.715
Then all tps features from the old Tails version are active 1.039
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 1.761
And the expected persistent files created with the old Tails version are present in the filesystem 1.018
And all persistent directories from the old Tails version have safe access rights 1.913
After features/support/hooks.rb:339 0.951
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:27.309
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.233
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.212
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.297
When the network is plugged 0.034
And Tor is ready 12.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.028
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.459
Given I shutdown Tails and wait for the computer to power off 5.233
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.471
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.671
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
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.082
# 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.161
When the network is plugged 0.024
And Tor is ready 10.294
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.891
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.837
Given I shutdown Tails and wait for the computer to power off 4.158
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.721
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.641
And the file system changes introduced in version 6.3~testoverlayfs are present 0.257
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.122
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.141
When the network is plugged 0.033
And Tor is ready 12.354
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.161
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.363
After features/support/hooks.rb:339 1.025
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.284
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.822
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.181
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 8.609
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.551
After features/support/hooks.rb:339 1.112
After features/support/hooks.rb:108 0.000