Project Number Date
test_Tails_ISO_stable-flatpak 17 14 Sep 2026, 19:53

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 12:47.802 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.898
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 14.679
When I start Tails from USB drive "old" with network unplugged 44.087
Then the boot device has safe access rights 2.268
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.077
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:339 1.780
After features/support/hooks.rb:108 0.007
Tags: @product
1:30.436
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.111
And I start Tails from USB drive "old" with network unplugged and I login 52.408
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 26.079
And I take note of which tps features are available 6.594
Then a Tails persistence partition exists on USB drive "old" 0.629
And I shutdown Tails and wait for the computer to power off 4.370
After features/support/hooks.rb:339 0.411
After features/support/hooks.rb:108 0.007
Tags: @product
1:43.374
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.565
Then Tails is running from USB drive "old" 0.215
And all tps features are active 9.669
When I write some files expected to persist 1.449
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 2.113
And I take note of which tps features are available 7.658
And I shutdown Tails and wait for the computer to power off 4.346
# 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.781
After features/support/hooks.rb:339 0.440
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.509
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 without a persistent partition and stopped at Tails Greeter's login screen 8.818
And I log in to a new session 12.700
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.671
And I plug USB drive "to_upgrade" 2.668
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.161
Then the running Tails is installed on USB drive "to_upgrade" 18.257
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.107
After features/support/hooks.rb:339 1.785
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.248
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 1:4.238
Then all tps features from the old Tails version are active 1.160
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 2.782
And the expected persistent files created with the old Tails version are present in the filesystem 1.483
And all persistent directories from the old Tails version have safe access rights 2.265
After features/support/hooks.rb:339 0.983
After features/support/hooks.rb:108 0.043
Tags: @product @automatic_upgrade
4:3.669
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.129
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.333
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.541
When the network is plugged 0.027
And Tor is ready 13.299
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.579
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.997
Given I shutdown Tails and wait for the computer to power off 7.164
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.780
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 9.255
And the file system changes introduced in version 6.2~testoverlayfs are present 0.263
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.214
When the network is plugged 0.038
And Tor is ready 10.408
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.551
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.294
Given I shutdown Tails and wait for the computer to power off 4.229
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.944
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 9.098
And the file system changes introduced in version 6.3~testoverlayfs are present 0.372
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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.039
And Tor is ready 10.618
Then the Upgrader considers the system as up-to-date 10.477
# 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.607
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.331
After features/support/hooks.rb:339 0.736
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
1:0.665
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 47.848
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 10.729
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.712
After features/support/hooks.rb:339 0.666
After features/support/hooks.rb:108 0.000