Project Number Date
test_Tails_ISO_stable-flatpak 1 08 Sep 2026, 12:25

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 12:17.796 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:16.534
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.139
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 14.338
When I start Tails from USB drive "old" with network unplugged 57.837
Then the boot device has safe access rights 2.542
And Tails is running from USB drive "old" 0.225
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.202
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 3.551
After features/support/hooks.rb:108 0.007
Tags: @product
1:32.694
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login 53.771
Then Tails is running from USB drive "old" 0.214
And I create a persistent partition 25.919
And I take note of which tps features are available 7.873
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 4.027
After features/support/hooks.rb:339 0.249
After features/support/hooks.rb:108 0.007
Tags: @product
1:42.250
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.817
Then Tails is running from USB drive "old" 0.274
And all tps features are active 8.723
When I write some files expected to persist 1.804
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.330
And all persistent directories from the old Tails version have safe access rights 2.508
And I take note of which tps features are available 7.061
And I shutdown Tails and wait for the computer to power off 2.741
# 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" 12.619
After features/support/hooks.rb:339 0.569
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.239
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.445
And I log in to a new session 11.837
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.645
And I plug USB drive "to_upgrade" 2.211
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.986
Then the running Tails is installed on USB drive "to_upgrade" 18.846
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 2.283
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.080
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.136
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.830
Then all tps features from the old Tails version are active 1.436
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 2.580
And the expected persistent files created with the old Tails version are present in the filesystem 1.453
And all persistent directories from the old Tails version have safe access rights 2.301
After features/support/hooks.rb:339 0.710
After features/support/hooks.rb:108 0.040
Tags: @product @automatic_upgrade
3:52.530
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.659
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.376
When the network is plugged 0.026
And Tor is ready 12.213
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.971
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.611
Given I shutdown Tails and wait for the computer to power off 5.654
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.636
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 8.501
And the file system changes introduced in version 6.2~testoverlayfs are present 0.213
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.100
# 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.216
When the network is plugged 0.039
And Tor is ready 10.652
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.113
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.411
Given I shutdown Tails and wait for the computer to power off 4.296
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.063
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 9.051
And the file system changes introduced in version 6.3~testoverlayfs are present 0.363
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.116
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.035
And Tor is ready 10.681
Then the Upgrader considers the system as up-to-date 0.125
# 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 4.059
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.443
After features/support/hooks.rb:339 0.892
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
21.466
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.599
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 9.196
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.288
After features/support/hooks.rb:339 0.972
After features/support/hooks.rb:108 0.000