Project Number Date
test_Tails_ISO_stable-flatpak 23 20 Sep 2026, 19:39

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 10:59.423 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:2.210
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 12.978
When I start Tails from USB drive "old" with network unplugged 45.567
Then the boot device has safe access rights 1.899
And Tails is running from USB drive "old" 0.264
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.029
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.119
After features/support/hooks.rb:339 1.706
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.991
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.142
And I start Tails from USB drive "old" with network unplugged and I login 46.670
Then Tails is running from USB drive "old" 0.207
And I create a persistent partition 23.627
And I take note of which tps features are available 5.979
Then a Tails persistence partition exists on USB drive "old" 0.510
And I shutdown Tails and wait for the computer to power off 3.853
After features/support/hooks.rb:339 0.333
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.783
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.286
Then Tails is running from USB drive "old" 0.224
And all tps features are active 6.931
When I write some files expected to persist 1.194
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.144
And all persistence configuration files have safe access rights 0.263
And all persistent directories from the old Tails version have safe access rights 1.632
And I take note of which tps features are available 5.870
And I shutdown Tails and wait for the computer to power off 5.053
# 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.098
After features/support/hooks.rb:339 0.482
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.240
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.322
And I log in to a new session 10.047
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.652
And I plug USB drive "to_upgrade" 2.211
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.649
Then the running Tails is installed on USB drive "to_upgrade" 17.109
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.116
After features/support/hooks.rb:339 1.734
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.320
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.329
Then all tps features from the old Tails version are active 1.113
And Tails is running from USB drive "to_upgrade" 0.204
And the boot device has safe access rights 1.924
And the expected persistent files created with the old Tails version are present in the filesystem 0.987
And all persistent directories from the old Tails version have safe access rights 1.679
After features/support/hooks.rb:339 0.837
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:27.113
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 7.913
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.261
When the network is plugged 0.023
And Tor is ready 12.355
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.769
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.132
Given I shutdown Tails and wait for the computer to power off 5.397
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.942
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.600
And the file system changes introduced in version 6.2~testoverlayfs are present 0.179
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.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.212
When the network is plugged 0.024
And Tor is ready 10.390
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.402
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.454
Given I shutdown Tails and wait for the computer to power off 3.821
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.422
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 7.928
And the file system changes introduced in version 6.3~testoverlayfs are present 0.302
And only the 6.3~testoverlayfs SquashFS delta is installed 0.029
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.163
When the network is plugged 0.027
And Tor is ready 10.314
Then the Upgrader considers the system as up-to-date 0.108
# 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.755
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.327
After features/support/hooks.rb:339 0.790
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.763
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.682
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 8.775
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.998
After features/support/hooks.rb:339 0.945
After features/support/hooks.rb:108 0.000