Project Number Date
test_Tails_ISO_21565-flatpak-safe 62 01 Oct 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 11:13.877 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:11.375
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.037
And I write an old version of the Tails USB image to disk "old" 13.489
When I start Tails from USB drive "old" with network unplugged 53.971
Then the boot device has safe access rights 2.186
And Tails is running from USB drive "old" 0.197
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.102
After features/support/hooks.rb:339 3.679
After features/support/hooks.rb:108 0.032
Tags: @product
1:20.574
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 46.723
Then Tails is running from USB drive "old" 0.218
And I create a persistent partition 22.555
And I take note of which tps features are available 6.467
Then a Tails persistence partition exists on USB drive "old" 0.466
And I shutdown Tails and wait for the computer to power off 4.071
After features/support/hooks.rb:339 0.295
After features/support/hooks.rb:108 0.005
Tags: @product
1:33.746
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:0.511
Then Tails is running from USB drive "old" 0.189
And all tps features are active 7.856
When I write some files expected to persist 1.299
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.175
And all persistence configuration files have safe access rights 0.284
And all persistent directories from the old Tails version have safe access rights 1.956
And I take note of which tps features are available 5.794
And I shutdown Tails and wait for the computer to power off 3.969
# 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.612
After features/support/hooks.rb:339 0.628
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.988
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.276
And I log in to a new session 12.103
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.690
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.193
Then the running Tails is installed on USB drive "to_upgrade" 18.187
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:339 1.768
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.709
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.111
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.750
Then all tps features from the old Tails version are active 1.235
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 2.220
And the expected persistent files created with the old Tails version are present in the filesystem 0.725
And all persistent directories from the old Tails version have safe access rights 1.460
After features/support/hooks.rb:339 0.471
After features/support/hooks.rb:108 0.006
3:26.545
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.285
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.205
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.347
When the network is plugged 0.026
And Tor is ready 13.412
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.374
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.869
Given I shutdown Tails and wait for the computer to power off 5.244
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.844
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 6.848
And the file system changes introduced in version 6.2~testoverlayfs are present 0.203
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.086
# 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.226
When the network is plugged 0.023
And Tor is ready 10.442
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.292
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.620
Given I shutdown Tails and wait for the computer to power off 2.525
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.119
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 9.892
And the file system changes introduced in version 6.3~testoverlayfs are present 0.323
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.093
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.036
And Tor is ready 10.309
Then the Upgrader considers the system as up-to-date 0.067
# 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.521
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.626
After features/support/hooks.rb:339 0.764
After features/support/hooks.rb:108 0.012
19.937
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.388
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.057
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.032
And Tor is ready 9.985
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.198
After features/support/hooks.rb:339 0.732
After features/support/hooks.rb:108 0.000