Project Number Date
test_Tails_ISO_stable-flatpak 7 09 Sep 2026, 14:49

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:29.802 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:13.081
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.683
When I start Tails from USB drive "old" with network unplugged 55.636
Then the boot device has safe access rights 1.971
And Tails is running from USB drive "old" 0.191
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.165
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:339 1.868
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.821
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login 49.020
Then Tails is running from USB drive "old" 0.234
And I create a persistent partition 24.412
And I take note of which tps features are available 6.400
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.082
After features/support/hooks.rb:339 0.501
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.495
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.902
Then Tails is running from USB drive "old" 0.231
And all tps features are active 7.050
When I write some files expected to persist 1.402
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.147
And all persistence configuration files have safe access rights 0.296
And all persistent directories from the old Tails version have safe access rights 1.950
And I take note of which tps features are available 6.172
And I shutdown Tails and wait for the computer to power off 2.517
# 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.721
After features/support/hooks.rb:339 0.350
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.167
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.374
And I log in to a new session 12.500
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.837
And I plug USB drive "to_upgrade" 2.180
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.458
Then the running Tails is installed on USB drive "to_upgrade" 18.579
And I unplug USB drive "to_upgrade" 0.110
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:339 0.603
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.839
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.020
Then all tps features from the old Tails version are active 1.104
And Tails is running from USB drive "to_upgrade" 0.226
And the boot device has safe access rights 2.201
And the expected persistent files created with the old Tails version are present in the filesystem 1.147
And all persistent directories from the old Tails version have safe access rights 2.058
After features/support/hooks.rb:339 0.901
After features/support/hooks.rb:108 0.005
3:36.727
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.790
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.185
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.244
When the network is plugged 0.026
And Tor is ready 13.388
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.596
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.907
Given I shutdown Tails and wait for the computer to power off 5.637
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.373
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.374
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.112
# 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.185
When the network is plugged 0.027
And Tor is ready 10.580
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.972
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.598
Given I shutdown Tails and wait for the computer to power off 3.829
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.322
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.866
And the file system changes introduced in version 6.3~testoverlayfs are present 0.278
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.078
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.158
When the network is plugged 0.036
And Tor is ready 11.447
Then the Upgrader considers the system as up-to-date 0.116
# 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.666
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.308
After features/support/hooks.rb:339 0.674
After features/support/hooks.rb:108 0.046
19.669
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.918
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.036
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.828
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.581
After features/support/hooks.rb:339 0.478
After features/support/hooks.rb:108 0.000