Project Number Date
test_Tails_ISO_21565-flatpak-safe 93 19 Oct 2026, 03:24

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.130 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.915
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.104
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.454
When I start Tails from USB drive "old" with network unplugged 53.355
Then the boot device has safe access rights 2.353
And Tails is running from USB drive "old" 0.200
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 3.649
After features/support/hooks.rb:108 0.018
Tags: @product
1:24.949
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 50.139
Then Tails is running from USB drive "old" 0.240
And I create a persistent partition 23.316
And I take note of which tps features are available 6.664
Then a Tails persistence partition exists on USB drive "old" 0.519
And I shutdown Tails and wait for the computer to power off 3.991
After features/support/hooks.rb:339 0.358
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.096
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.157
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.612
Then Tails is running from USB drive "old" 0.203
And all tps features are active 7.100
When I write some files expected to persist 1.269
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.297
And all persistent directories from the old Tails version have safe access rights 1.794
And I take note of which tps features are available 6.348
And I shutdown Tails and wait for the computer to power off 2.573
# 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.577
After features/support/hooks.rb:339 0.174
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.573
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.432
And I log in to a new session 12.099
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.824
And I plug USB drive "to_upgrade" 2.287
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.520
Then the running Tails is installed on USB drive "to_upgrade" 18.116
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 1.498
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.161
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.508
Then all tps features from the old Tails version are active 1.084
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.577
And the expected persistent files created with the old Tails version are present in the filesystem 0.976
And all persistent directories from the old Tails version have safe access rights 1.696
After features/support/hooks.rb:339 0.476
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
3:26.166
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.116
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.221
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.321
When the network is plugged 0.032
And Tor is ready 13.012
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.346
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.379
Given I shutdown Tails and wait for the computer to power off 5.229
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.348
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.079
And the file system changes introduced in version 6.2~testoverlayfs are present 0.176
And only the 6.2~testoverlayfs SquashFS delta is installed 0.032
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.095
# 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.209
When the network is plugged 0.025
And Tor is ready 11.295
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.536
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.929
Given I shutdown Tails and wait for the computer to power off 3.996
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.184
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.813
And the file system changes introduced in version 6.3~testoverlayfs are present 0.356
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.082
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.145
When the network is plugged 0.034
And Tor is ready 10.408
Then the Upgrader considers the system as up-to-date 0.109
# 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.046
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.250
After features/support/hooks.rb:339 0.621
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.267
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 7.791
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
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.032
And Tor is ready 8.581
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.422
After features/support/hooks.rb:339 0.926
After features/support/hooks.rb:108 0.000