Project Number Date
test_Tails_ISO_21565-flatpak-safe 22 01 Sep 2026, 03:15

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 10:58.082 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:6.207
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.494
When I start Tails from USB drive "old" with network unplugged 48.847
Then the boot device has safe access rights 2.111
And Tails is running from USB drive "old" 0.224
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 3.841
After features/support/hooks.rb:108 0.050
Tags: @product
1:20.356
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 47.100
Then Tails is running from USB drive "old" 0.219
And I create a persistent partition 22.348
And I take note of which tps features are available 6.211
Then a Tails persistence partition exists on USB drive "old" 0.510
And I shutdown Tails and wait for the computer to power off 3.891
After features/support/hooks.rb:339 0.473
After features/support/hooks.rb:108 0.006
Tags: @product
1:26.796
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.153
Then Tails is running from USB drive "old" 0.175
And all tps features are active 6.791
When I write some files expected to persist 0.970
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.136
And all persistence configuration files have safe access rights 0.188
And all persistent directories from the old Tails version have safe access rights 1.619
And I take note of which tps features are available 6.149
And I shutdown Tails and wait for the computer to power off 2.556
# 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" 10.966
After features/support/hooks.rb:339 0.534
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.257
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.314
And I log in to a new session 11.487
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.613
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.555
Then the running Tails is installed on USB drive "to_upgrade" 17.814
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 1.629
After features/support/hooks.rb:108 0.000
Tags: @product
1:2.847
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 57.434
Then all tps features from the old Tails version are active 0.993
And Tails is running from USB drive "to_upgrade" 0.185
And the boot device has safe access rights 1.770
And the expected persistent files created with the old Tails version are present in the filesystem 0.878
And all persistent directories from the old Tails version have safe access rights 1.510
After features/support/hooks.rb:339 0.758
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:32.282
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.206
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.185
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.280
When the network is plugged 0.026
And Tor is ready 12.505
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.006
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.891
Given I shutdown Tails and wait for the computer to power off 5.184
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.260
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 6.963
And the file system changes introduced in version 6.2~testoverlayfs are present 0.201
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.111
# 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.175
When the network is plugged 0.035
And Tor is ready 9.953
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.469
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.871
Given I shutdown Tails and wait for the computer to power off 2.537
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.014
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.449
And the file system changes introduced in version 6.3~testoverlayfs are present 0.336
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.116
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.160
When the network is plugged 0.032
And Tor is ready 10.091
Then the Upgrader considers the system as up-to-date 10.379
# 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.099
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.331
After features/support/hooks.rb:339 0.559
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
18.333
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.748
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
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.040
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 8.242
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.988
After features/support/hooks.rb:339 0.805
After features/support/hooks.rb:108 0.000