Project Number Date
test_Tails_ISO_21565-flatpak-safe 84 11 Oct 2026, 03:26

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:44.107 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:22.640
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.034
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.440
When I start Tails from USB drive "old" with network unplugged 1:5.079
Then the boot device has safe access rights 2.431
And Tails is running from USB drive "old" 0.187
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.145
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 3.432
After features/support/hooks.rb:108 0.051
Tags: @product
1:21.887
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 49.017
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 23.089
And I take note of which tps features are available 6.332
Then a Tails persistence partition exists on USB drive "old" 0.499
And I shutdown Tails and wait for the computer to power off 2.638
After features/support/hooks.rb:339 0.503
After features/support/hooks.rb:108 0.005
Tags: @product
1:36.017
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.918
Then Tails is running from USB drive "old" 0.332
And all tps features are active 8.260
When I write some files expected to persist 1.173
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.143
And all persistence configuration files have safe access rights 0.288
And all persistent directories from the old Tails version have safe access rights 1.598
And I take note of which tps features are available 6.382
And I shutdown Tails and wait for the computer to power off 4.304
# 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.516
After features/support/hooks.rb:339 0.333
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.732
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.371
And I log in to a new session 11.486
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.882
And I plug USB drive "to_upgrade" 2.334
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.519
Then the running Tails is installed on USB drive "to_upgrade" 17.883
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:339 0.572
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.908
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.491
Then all tps features from the old Tails version are active 1.099
And Tails is running from USB drive "to_upgrade" 0.250
And the boot device has safe access rights 2.250
And the expected persistent files created with the old Tails version are present in the filesystem 0.930
And all persistent directories from the old Tails version have safe access rights 1.793
After features/support/hooks.rb:339 0.803
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:41.458
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.616
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.175
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.418
When the network is plugged 0.035
And Tor is ready 12.933
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.188
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.411
Given I shutdown Tails and wait for the computer to power off 5.429
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.985
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.211
And the file system changes introduced in version 6.2~testoverlayfs are present 0.242
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.169
When the network is plugged 0.034
And Tor is ready 10.173
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.909
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.992
Given I shutdown Tails and wait for the computer to power off 5.262
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.048
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.634
And the file system changes introduced in version 6.3~testoverlayfs are present 0.321
And only the 6.3~testoverlayfs SquashFS delta is installed 0.028
# 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.076
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.023
And Tor is ready 9.434
Then the Upgrader considers the system as up-to-date 10.423
# 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.136
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.346
After features/support/hooks.rb:339 0.984
After features/support/hooks.rb:108 0.049
Tags: @product @automatic_upgrade
20.462
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 with a persistent partition enabled and logged in 8.226
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 10.717
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.184
After features/support/hooks.rb:339 0.742
After features/support/hooks.rb:108 0.000