Project Number Date
test_Tails_ISO_stable-flatpak 20 17 Sep 2026, 19:57

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:42.303 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:15.356
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.052
When I start Tails from USB drive "old" with network unplugged 57.603
Then the boot device has safe access rights 1.991
And Tails is running from USB drive "old" 0.210
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.030
And udev-watchdog is monitoring the correct device 0.182
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 3.723
After features/support/hooks.rb:108 0.008
Tags: @product
1:23.486
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login 48.706
Then Tails is running from USB drive "old" 0.206
And I create a persistent partition 24.122
And I take note of which tps features are available 7.292
Then a Tails persistence partition exists on USB drive "old" 0.505
And I shutdown Tails and wait for the computer to power off 2.545
After features/support/hooks.rb:339 0.371
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.605
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.113
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.417
Then Tails is running from USB drive "old" 0.199
And all tps features are active 8.797
When I write some files expected to persist 1.355
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.347
And all persistent directories from the old Tails version have safe access rights 1.845
And I take note of which tps features are available 6.970
And I shutdown Tails and wait for the computer to power off 3.987
# 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.412
After features/support/hooks.rb:339 0.216
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.981
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.687
And I log in to a new session 12.895
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.777
And I plug USB drive "to_upgrade" 2.248
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.650
Then the running Tails is installed on USB drive "to_upgrade" 17.468
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.116
After features/support/hooks.rb:339 1.889
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.134
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.398
Then all tps features from the old Tails version are active 1.110
And Tails is running from USB drive "to_upgrade" 0.189
And the boot device has safe access rights 2.343
And the expected persistent files created with the old Tails version are present in the filesystem 1.098
And all persistent directories from the old Tails version have safe access rights 1.913
After features/support/hooks.rb:339 0.534
After features/support/hooks.rb:108 0.029
Tags: @product @automatic_upgrade
3:40.977
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.581
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.329
When the network is plugged 0.033
And Tor is ready 12.821
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.825
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.394
Given I shutdown Tails and wait for the computer to power off 6.626
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.613
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.231
And the file system changes introduced in version 6.2~testoverlayfs are present 0.146
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.103
# 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.189
When the network is plugged 0.033
And Tor is ready 10.942
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.623
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.592
Given I shutdown Tails and wait for the computer to power off 4.190
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.998
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 8.109
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.167
When the network is plugged 0.032
And Tor is ready 10.853
Then the Upgrader considers the system as up-to-date 0.092
# 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.888
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.330
After features/support/hooks.rb:339 0.924
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.759
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.893
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.032
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 10.401
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.163
After features/support/hooks.rb:339 0.953
After features/support/hooks.rb:108 0.000