Project Number Date
test_Tails_ISO_21548-flatpak-install 7 17 May 2026, 14:16

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:3.319 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:3.469
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.046
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 12.482
When I start Tails from USB drive "old" with network unplugged 46.512
Then the boot device has safe access rights 2.726
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:335 1.398
After features/support/hooks.rb:104 0.006
Tags: @product
1:25.597
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 52.342
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 24.141
And I take note of which tps features are available 0.395
Then a Tails persistence partition exists on USB drive "old" 0.556
And I shutdown Tails and wait for the computer to power off 7.844
After features/support/hooks.rb:335 0.273
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.842
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.004
Then Tails is running from USB drive "old" 0.257
And all tps features are active 1.074
When I write some files expected to persist 1.162
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.266
And all persistent directories from the old Tails version have safe access rights 2.027
And I take note of which tps features are available 0.152
And I shutdown Tails and wait for the computer to power off 7.952
# 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.689
After features/support/hooks.rb:335 0.567
After features/support/hooks.rb:104 0.009
Tags: @product
2:9.193
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 7.638
And I log in to a new session 12.307
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.687
And I plug USB drive "to_upgrade" 2.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.611
Then the running Tails is installed on USB drive "to_upgrade" 15.445
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:335 0.673
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.113
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.568
Then all tps features from the old Tails version are active 0.910
And Tails is running from USB drive "to_upgrade" 0.257
And the boot device has safe access rights 2.382
And the expected persistent files created with the old Tails version are present in the filesystem 1.110
And all persistent directories from the old Tails version have safe access rights 1.833
After features/support/hooks.rb:335 0.601
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:32.708
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.294
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
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.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.342
When the network is plugged 0.016
And Tor is ready 13.212
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.373
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.667
Given I shutdown Tails and wait for the computer to power off 9.361
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.097
Then Tails is running version 6.2~testoverlayfs 0.041
And all tps features are active 1.159
And the file system changes introduced in version 6.2~testoverlayfs are present 0.197
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.211
When the network is plugged 0.015
And Tor is ready 9.888
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.901
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.220
Given I shutdown Tails and wait for the computer to power off 4.304
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.076
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.216
And the file system changes introduced in version 6.3~testoverlayfs are present 0.385
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.247
When the network is plugged 0.018
And Tor is ready 10.458
Then the Upgrader considers the system as up-to-date 10.512
# 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 4.128
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:335 0.639
After features/support/hooks.rb:104 0.016
Tags: @product @automatic_upgrade
20.394
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.162
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 9.866
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.905
After features/support/hooks.rb:335 0.791
After features/support/hooks.rb:104 0.000