Project Number Date
test_Tails_ISO_stable-flatpak 6 08 Sep 2026, 20:11

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:1.903 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.132
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 15.292
When I start Tails from USB drive "old" with network unplugged 56.242
Then the boot device has safe access rights 2.798
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.228
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.480
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.247
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login 51.902
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 24.500
And I take note of which tps features are available 6.818
Then a Tails persistence partition exists on USB drive "old" 0.519
And I shutdown Tails and wait for the computer to power off 4.170
After features/support/hooks.rb:339 0.596
After features/support/hooks.rb:108 0.016
Tags: @product
1:42.581
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.383
Then Tails is running from USB drive "old" 0.240
And all tps features are active 10.691
When I write some files expected to persist 1.336
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.129
And all persistence configuration files have safe access rights 0.263
And all persistent directories from the old Tails version have safe access rights 1.787
And I take note of which tps features are available 7.032
And I shutdown Tails and wait for the computer to power off 3.901
# 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.728
After features/support/hooks.rb:339 0.232
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.193
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.631
And I log in to a new session 13.326
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.695
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.015
Then the running Tails is installed on USB drive "to_upgrade" 18.051
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 0.681
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.673
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.046
Then all tps features from the old Tails version are active 1.218
And Tails is running from USB drive "to_upgrade" 0.254
And the boot device has safe access rights 2.545
And the expected persistent files created with the old Tails version are present in the filesystem 1.431
And all persistent directories from the old Tails version have safe access rights 2.095
After features/support/hooks.rb:339 0.467
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:45.264
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 with a persistent partition enabled and logged in 8.435
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.390
When the network is plugged 0.024
And Tor is ready 13.766
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.418
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.374
Given I shutdown Tails and wait for the computer to power off 5.719
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.422
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.831
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.165
When the network is plugged 0.030
And Tor is ready 11.013
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.568
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.515
Given I shutdown Tails and wait for the computer to power off 4.092
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.536
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.771
And the file system changes introduced in version 6.3~testoverlayfs are present 0.277
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.038
And Tor is ready 12.327
Then the Upgrader considers the system as up-to-date 0.118
# 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.544
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.387
After features/support/hooks.rb:339 1.026
After features/support/hooks.rb:108 0.036
Tags: @product @automatic_upgrade
21.809
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.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 11.033
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.308
After features/support/hooks.rb:339 1.002
After features/support/hooks.rb:108 0.000