Project Number Date
test_Tails_ISO_stable-flatpak 32 30 Sep 2026, 19:47

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:16.857 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:10.042
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.105
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.820
When I start Tails from USB drive "old" with network unplugged 51.294
Then the boot device has safe access rights 3.130
And Tails is running from USB drive "old" 0.219
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.106
After features/support/hooks.rb:339 3.574
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.263
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 51.676
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 24.859
And I take note of which tps features are available 6.760
Then a Tails persistence partition exists on USB drive "old" 0.581
And I shutdown Tails and wait for the computer to power off 4.050
After features/support/hooks.rb:339 0.628
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.375
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.621
Then Tails is running from USB drive "old" 0.232
And all tps features are active 7.338
When I write some files expected to persist 1.399
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.145
And all persistence configuration files have safe access rights 0.283
And all persistent directories from the old Tails version have safe access rights 2.089
And I take note of which tps features are available 5.647
And I shutdown Tails and wait for the computer to power off 4.296
# 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.209
After features/support/hooks.rb:339 0.443
After features/support/hooks.rb:108 0.007
Tags: @product
2:15.491
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 without a persistent partition and stopped at Tails Greeter's login screen 8.454
And I log in to a new session 12.973
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.668
And I plug USB drive "to_upgrade" 2.252
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.590
Then the running Tails is installed on USB drive "to_upgrade" 19.306
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.861
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.522
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.100
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.406
Then all tps features from the old Tails version are active 1.512
And Tails is running from USB drive "to_upgrade" 0.221
And the boot device has safe access rights 2.629
And the expected persistent files created with the old Tails version are present in the filesystem 1.312
And all persistent directories from the old Tails version have safe access rights 2.339
After features/support/hooks.rb:339 0.750
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
3:45.051
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.547
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.303
When the network is plugged 0.034
And Tor is ready 14.059
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.452
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.949
Given I shutdown Tails and wait for the computer to power off 5.497
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.039
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.183
And the file system changes introduced in version 6.2~testoverlayfs are present 0.274
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# 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.215
When the network is plugged 0.024
And Tor is ready 11.431
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.614
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.406
Given I shutdown Tails and wait for the computer to power off 3.973
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.772
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.635
And the file system changes introduced in version 6.3~testoverlayfs are present 0.307
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.088
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.033
And Tor is ready 11.465
Then the Upgrader considers the system as up-to-date 0.111
# 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.328
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.822
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
46.111
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 34.791
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
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.048
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 8.848
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.116
After features/support/hooks.rb:339 0.811
After features/support/hooks.rb:108 0.000