Project Number Date
test_Tails_ISO_21565-flatpak-safe 74 06 Oct 2026, 13:52

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:24.651 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:31.903
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.659
When I start Tails from USB drive "old" with network unplugged 1:12.414
Then the boot device has safe access rights 2.864
And Tails is running from USB drive "old" 0.210
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:339 1.488
After features/support/hooks.rb:108 0.007
Tags: @product
1:31.613
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.111
And I start Tails from USB drive "old" with network unplugged and I login 52.164
Then Tails is running from USB drive "old" 0.223
And I create a persistent partition 27.245
And I take note of which tps features are available 7.307
Then a Tails persistence partition exists on USB drive "old" 0.588
And I shutdown Tails and wait for the computer to power off 3.972
After features/support/hooks.rb:339 0.253
After features/support/hooks.rb:108 0.006
Tags: @product
1:40.796
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.591
Then Tails is running from USB drive "old" 0.258
And all tps features are active 7.805
When I write some files expected to persist 1.168
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.358
And all persistent directories from the old Tails version have safe access rights 1.812
And I take note of which tps features are available 6.249
And I shutdown Tails and wait for the computer to power off 5.167
# 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" 13.099
After features/support/hooks.rb:339 0.543
After features/support/hooks.rb:108 0.006
Tags: @product
2:19.281
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 without a persistent partition and stopped at Tails Greeter's login screen 9.240
And I log in to a new session 13.684
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.868
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.334
Then the running Tails is installed on USB drive "to_upgrade" 19.712
And I unplug USB drive "to_upgrade" 0.112
And I unplug USB drive "__internal" 0.107
After features/support/hooks.rb:339 1.881
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.935
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.105
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.377
Then all tps features from the old Tails version are active 1.132
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.460
And the expected persistent files created with the old Tails version are present in the filesystem 1.001
And all persistent directories from the old Tails version have safe access rights 1.636
After features/support/hooks.rb:339 0.788
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:48.997
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.284
And no SquashFS delta is installed 0.092
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.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.036
And Tor is ready 12.289
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.034
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.590
Given I shutdown Tails and wait for the computer to power off 5.610
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.566
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.168
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.240
When the network is plugged 0.027
And Tor is ready 10.777
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.387
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.410
Given I shutdown Tails and wait for the computer to power off 4.045
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.700
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 8.776
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.023
And Tor is ready 10.461
Then the Upgrader considers the system as up-to-date 0.092
# 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.709
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.344
After features/support/hooks.rb:339 0.942
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.124
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.782
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
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.044
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 9.987
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.967
After features/support/hooks.rb:339 0.604
After features/support/hooks.rb:108 0.000