Project Number Date
test_Tails_ISO_21565-flatpak-safe 121 04 Nov 2026, 03:29

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:12.011 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:12.812
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.070
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.238
When I start Tails from USB drive "old" with network unplugged 55.648
Then the boot device has safe access rights 2.212
And Tails is running from USB drive "old" 0.203
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 3.723
After features/support/hooks.rb:108 0.017
Tags: @product
1:19.753
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 "old" with network unplugged and I login 47.226
Then Tails is running from USB drive "old" 0.187
And I create a persistent partition 22.610
And I take note of which tps features are available 6.555
Then a Tails persistence partition exists on USB drive "old" 0.517
And I shutdown Tails and wait for the computer to power off 2.574
After features/support/hooks.rb:339 0.541
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.201
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.024
Then Tails is running from USB drive "old" 0.193
And all tps features are active 6.679
When I write some files expected to persist 0.984
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.149
And all persistence configuration files have safe access rights 0.307
And all persistent directories from the old Tails version have safe access rights 1.411
And I take note of which tps features are available 5.982
And I shutdown Tails and wait for the computer to power off 5.212
# 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.175
After features/support/hooks.rb:339 0.633
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.907
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.281
And I log in to a new session 11.296
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.678
And I plug USB drive "to_upgrade" 2.198
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.933
Then the running Tails is installed on USB drive "to_upgrade" 18.288
And I unplug USB drive "to_upgrade" 0.107
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 3.632
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.341
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.764
Then all tps features from the old Tails version are active 1.004
And Tails is running from USB drive "to_upgrade" 0.177
And the boot device has safe access rights 1.908
And the expected persistent files created with the old Tails version are present in the filesystem 0.894
And all persistent directories from the old Tails version have safe access rights 1.506
After features/support/hooks.rb:339 0.809
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:31.403
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.993
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.188
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.196
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.258
When the network is plugged 0.036
And Tor is ready 12.610
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.977
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 3.713
Given I shutdown Tails and wait for the computer to power off 5.173
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.875
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.938
And the file system changes introduced in version 6.2~testoverlayfs are present 0.170
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.101
# 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.143
When the network is plugged 0.034
And Tor is ready 10.300
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.539
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.467
Given I shutdown Tails and wait for the computer to power off 2.576
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.649
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 7.575
And the file system changes introduced in version 6.3~testoverlayfs are present 0.400
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.090
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.176
When the network is plugged 0.037
And Tor is ready 10.064
Then the Upgrader considers the system as up-to-date 10.403
# 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.199
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.314
After features/support/hooks.rb:339 0.977
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.592
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.699
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.041
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 9.650
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.878
After features/support/hooks.rb:339 0.588
After features/support/hooks.rb:108 0.000