Project Number Date
test_Tails_ISO_21565-flatpak-safe 37 17 Sep 2026, 03:21

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:6.092 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:7.120
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
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.129
When I start Tails from USB drive "old" with network unplugged 50.067
Then the boot device has safe access rights 2.008
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.270
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 1.149
After features/support/hooks.rb:108 0.017
Tags: @product
1:17.723
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 46.653
Then Tails is running from USB drive "old" 0.201
And I create a persistent partition 22.122
And I take note of which tps features are available 5.644
Then a Tails persistence partition exists on USB drive "old" 0.459
And I shutdown Tails and wait for the computer to power off 2.558
After features/support/hooks.rb:339 0.689
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.827
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.203
Then Tails is running from USB drive "old" 0.204
And all tps features are active 7.238
When I write some files expected to persist 0.978
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.105
And all persistence configuration files have safe access rights 0.283
And all persistent directories from the old Tails version have safe access rights 1.498
And I take note of which tps features are available 5.559
And I shutdown Tails and wait for the computer to power off 2.496
# 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.182
After features/support/hooks.rb:339 0.446
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.604
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.237
And I log in to a new session 12.103
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.606
And I plug USB drive "to_upgrade" 2.365
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.970
Then the running Tails is installed on USB drive "to_upgrade" 18.092
And I unplug USB drive "to_upgrade" 0.114
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 1.944
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.200
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.912
Then all tps features from the old Tails version are active 0.927
And Tails is running from USB drive "to_upgrade" 0.169
And the boot device has safe access rights 1.921
And the expected persistent files created with the old Tails version are present in the filesystem 0.793
And all persistent directories from the old Tails version have safe access rights 1.397
After features/support/hooks.rb:339 0.424
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:34.021
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 20.843
And no SquashFS delta is installed 0.048
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.176
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.203
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.329
When the network is plugged 0.033
And Tor is ready 11.810
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.436
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 3.865
Given I shutdown Tails and wait for the computer to power off 5.133
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.842
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.457
And the file system changes introduced in version 6.2~testoverlayfs are present 0.198
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.100
# 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.181
When the network is plugged 0.030
And Tor is ready 10.127
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.988
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.389
Given I shutdown Tails and wait for the computer to power off 4.153
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.451
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.446
And the file system changes introduced in version 6.3~testoverlayfs are present 0.330
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.150
When the network is plugged 0.033
And Tor is ready 10.266
Then the Upgrader considers the system as up-to-date 0.194
# 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.190
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.317
After features/support/hooks.rb:339 0.888
After features/support/hooks.rb:108 0.031
Tags: @product @automatic_upgrade
19.594
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.760
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 9.991
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.531
After features/support/hooks.rb:339 0.599
After features/support/hooks.rb:108 0.000