Project Number Date
test_Tails_ISO_stable-flatpak 56 25 Oct 2026, 19:42

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:0.202 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:8.575
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.088
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.196
When I start Tails from USB drive "old" with network unplugged 51.920
Then the boot device has safe access rights 1.794
And Tails is running from USB drive "old" 0.197
And there is no persistence partition on USB drive "old" 0.030
And process "udev-watchdog" is running 0.028
And udev-watchdog is monitoring the correct device 0.170
And I unplug USB drive "old" 0.105
After features/support/hooks.rb:339 3.417
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.147
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 48.174
Then Tails is running from USB drive "old" 0.203
And I create a persistent partition 23.626
And I take note of which tps features are available 5.982
Then a Tails persistence partition exists on USB drive "old" 0.523
And I shutdown Tails and wait for the computer to power off 2.562
After features/support/hooks.rb:339 0.250
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.825
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.112
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.141
Then Tails is running from USB drive "old" 0.183
And all tps features are active 7.170
When I write some files expected to persist 1.226
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.109
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 1.794
And I take note of which tps features are available 5.798
And I shutdown Tails and wait for the computer to power off 2.538
# 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.446
After features/support/hooks.rb:339 0.446
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.191
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.194
And I log in to a new session 11.823
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.646
And I plug USB drive "to_upgrade" 2.200
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.706
Then the running Tails is installed on USB drive "to_upgrade" 17.378
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.569
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.657
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.254
Then all tps features from the old Tails version are active 1.071
And Tails is running from USB drive "to_upgrade" 0.186
And the boot device has safe access rights 2.035
And the expected persistent files created with the old Tails version are present in the filesystem 1.160
And all persistent directories from the old Tails version have safe access rights 1.875
After features/support/hooks.rb:339 0.558
After features/support/hooks.rb:108 0.027
Tags: @product @automatic_upgrade
3:24.376
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.807
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.168
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.183
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.257
When the network is plugged 0.022
And Tor is ready 12.574
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.427
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.139
Given I shutdown Tails and wait for the computer to power off 5.218
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.278
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.318
And the file system changes introduced in version 6.2~testoverlayfs are present 0.179
And only the 6.2~testoverlayfs SquashFS delta is installed 0.035
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.099
# 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.166
When the network is plugged 0.031
And Tor is ready 10.306
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.930
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.228
Given I shutdown Tails and wait for the computer to power off 2.521
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.233
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.227
And the file system changes introduced in version 6.3~testoverlayfs are present 0.251
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.103
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.164
When the network is plugged 0.027
And Tor is ready 11.296
Then the Upgrader considers the system as up-to-date 0.149
# 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.489
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.374
After features/support/hooks.rb:339 0.923
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
19.429
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.545
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.033
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 9.569
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.995
After features/support/hooks.rb:339 0.829
After features/support/hooks.rb:108 0.000