Project Number Date
test_Tails_ISO_21565-flatpak-safe 80 08 Oct 2026, 14:03

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:26.366 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:9.732
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 13.597
When I start Tails from USB drive "old" with network unplugged 52.391
Then the boot device has safe access rights 2.027
And Tails is running from USB drive "old" 0.201
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.167
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 1.653
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.030
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 48.910
Then Tails is running from USB drive "old" 0.196
And I create a persistent partition 23.814
And I take note of which tps features are available 7.323
Then a Tails persistence partition exists on USB drive "old" 0.558
And I shutdown Tails and wait for the computer to power off 4.148
After features/support/hooks.rb:339 0.310
After features/support/hooks.rb:108 0.008
Tags: @product
1:33.952
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.417
Then Tails is running from USB drive "old" 0.260
And all tps features are active 7.700
When I write some files expected to persist 1.223
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.503
And all persistent directories from the old Tails version have safe access rights 1.789
And I take note of which tps features are available 7.333
And I shutdown Tails and wait for the computer to power off 2.575
# 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.859
After features/support/hooks.rb:339 0.348
After features/support/hooks.rb:108 0.007
Tags: @product
2:15.363
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 8.474
And I log in to a new session 14.351
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.814
And I plug USB drive "to_upgrade" 2.221
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.951
Then the running Tails is installed on USB drive "to_upgrade" 18.310
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.117
After features/support/hooks.rb:339 3.881
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.175
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.139
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.949
Then all tps features from the old Tails version are active 1.137
And Tails is running from USB drive "to_upgrade" 0.224
And the boot device has safe access rights 2.182
And the expected persistent files created with the old Tails version are present in the filesystem 0.970
And all persistent directories from the old Tails version have safe access rights 1.571
After features/support/hooks.rb:339 0.506
After features/support/hooks.rb:108 0.047
Tags: @product @automatic_upgrade
3:32.912
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.295
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.379
When the network is plugged 0.032
And Tor is ready 13.362
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.389
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.903
Given I shutdown Tails and wait for the computer to power off 5.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.321
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.313
And the file system changes introduced in version 6.2~testoverlayfs are present 0.255
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.109
# 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.177
When the network is plugged 0.030
And Tor is ready 10.354
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.315
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.284
Given I shutdown Tails and wait for the computer to power off 2.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.725
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.317
And the file system changes introduced in version 6.3~testoverlayfs are present 0.300
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.102
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186
When the network is plugged 0.034
And Tor is ready 10.873
Then the Upgrader considers the system as up-to-date 0.115
# 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.646
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.362
After features/support/hooks.rb:339 0.927
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
18.199
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.740
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
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.042
And Tor is ready 8.560
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.560
After features/support/hooks.rb:339 1.058
After features/support/hooks.rb:108 0.000