Project Number Date
test_Tails_ISO_21565-flatpak-safe 96 22 Oct 2026, 03:26

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:18.193 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:17.072
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.124
When I start Tails from USB drive "old" with network unplugged 1:0.352
Then the boot device has safe access rights 1.870
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.480
After features/support/hooks.rb:108 0.040
Tags: @product
1:19.605
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 46.722
Then Tails is running from USB drive "old" 0.176
And I create a persistent partition 22.029
And I take note of which tps features are available 6.114
Then a Tails persistence partition exists on USB drive "old" 0.466
And I shutdown Tails and wait for the computer to power off 4.025
After features/support/hooks.rb:339 0.233
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.796
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.154
Then Tails is running from USB drive "old" 0.235
And all tps features are active 6.901
When I write some files expected to persist 1.059
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.137
And all persistence configuration files have safe access rights 0.251
And all persistent directories from the old Tails version have safe access rights 1.427
And I take note of which tps features are available 5.538
And I shutdown Tails and wait for the computer to power off 2.598
# 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.314
After features/support/hooks.rb:339 0.458
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.947
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.179
And I log in to a new session 12.764
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.710
And I plug USB drive "to_upgrade" 2.610
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.785
Then the running Tails is installed on USB drive "to_upgrade" 17.634
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 2.058
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.312
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.091
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.545
Then all tps features from the old Tails version are active 1.036
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 1.983
And the expected persistent files created with the old Tails version are present in the filesystem 0.900
And all persistent directories from the old Tails version have safe access rights 1.543
After features/support/hooks.rb:339 0.913
After features/support/hooks.rb:108 0.005
3:23.017
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.872
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.171
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.291
When the network is plugged 0.034
And Tor is ready 13.299
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.862
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.554
Given I shutdown Tails and wait for the computer to power off 5.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.682
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 7.055
And the file system changes introduced in version 6.2~testoverlayfs are present 0.190
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.107
# 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.157
When the network is plugged 0.032
And Tor is ready 10.239
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.865
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.466
Given I shutdown Tails and wait for the computer to power off 3.953
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.925
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.116
And the file system changes introduced in version 6.3~testoverlayfs are present 0.293
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.099
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.235
When the network is plugged 0.032
And Tor is ready 10.352
Then the Upgrader considers the system as up-to-date 0.075
# 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.074
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.297
After features/support/hooks.rb:339 0.749
After features/support/hooks.rb:108 0.009
31.440
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.642
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 8.386
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.042
After features/support/hooks.rb:339 0.692
After features/support/hooks.rb:108 0.000