Project Number Date
test_Tails_ISO_flatpak-whisperback 1 11 May 2026, 18: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 13:18.130 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.954
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.061
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 15.050
When I start Tails from USB drive "old" with network unplugged 49.324
Then the boot device has safe access rights 3.535
And Tails is running from USB drive "old" 0.365
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.237
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:331 3.831
After features/support/hooks.rb:100 0.009
Tags: @product
1:32.201
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login 1:0.200
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 26.103
And I take note of which tps features are available 0.722
Then a Tails persistence partition exists on USB drive "old" 0.589
And I shutdown Tails and wait for the computer to power off 4.201
After features/support/hooks.rb:331 0.204
After features/support/hooks.rb:100 0.012
Tags: @product
1:35.241
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.432
Then Tails is running from USB drive "old" 0.289
And all tps features are active 1.236
When I write some files expected to persist 1.565
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.287
And all persistence configuration files have safe access rights 0.641
And all persistent directories from the old Tails version have safe access rights 2.071
And I take note of which tps features are available 0.179
And I shutdown Tails and wait for the computer to power off 8.693
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.780
After features/support/hooks.rb:331 0.140
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.434
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.017
And I log in to a new session 13.216
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.029
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.161
Then the running Tails is installed on USB drive "to_upgrade" 18.504
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 2.262
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.568
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.423
Then all tps features from the old Tails version are active 1.266
And Tails is running from USB drive "to_upgrade" 0.250
And the boot device has safe access rights 2.960
And the expected persistent files created with the old Tails version are present in the filesystem 1.302
And all persistent directories from the old Tails version have safe access rights 2.287
After features/support/hooks.rb:331 0.704
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
5:1.262
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.634
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.392
When the network is plugged 0.018
And Tor is ready 23.244
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.415
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.279
Given I shutdown Tails and wait for the computer to power off 20.507
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.744
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.680
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.231
When the network is plugged 0.016
And Tor is ready 23.017
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.503
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.236
Given I shutdown Tails and wait for the computer to power off 18.781
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.409
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.198
And the file system changes introduced in version 6.3~testoverlayfs are present 0.349
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.182
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.239
When the network is plugged 0.020
And Tor is ready 20.780
Then the Upgrader considers the system as up-to-date 0.170
# 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 5.604
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.464
After features/support/hooks.rb:331 0.716
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
27.466
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.628
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 19.068
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.400
After features/support/hooks.rb:331 0.794
After features/support/hooks.rb:100 0.000