Project Number Date
test_Tails_ISO_stable-flatpak 11 09 Sep 2026, 22:02

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:23.535 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:8.404
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.102
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.133
When I start Tails from USB drive "old" with network unplugged 51.458
Then the boot device has safe access rights 2.032
And Tails is running from USB drive "old" 0.232
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.171
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:339 1.530
After features/support/hooks.rb:108 0.005
Tags: @product
1:25.842
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login 49.755
Then Tails is running from USB drive "old" 0.276
And I create a persistent partition 24.549
And I take note of which tps features are available 6.562
Then a Tails persistence partition exists on USB drive "old" 0.573
And I shutdown Tails and wait for the computer to power off 4.034
After features/support/hooks.rb:339 0.481
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.044
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.330
Then Tails is running from USB drive "old" 0.243
And all tps features are active 7.540
When I write some files expected to persist 1.269
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.129
And all persistence configuration files have safe access rights 0.259
And all persistent directories from the old Tails version have safe access rights 1.901
And I take note of which tps features are available 5.970
And I shutdown Tails and wait for the computer to power off 3.869
# 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.425
After features/support/hooks.rb:339 0.226
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.954
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.605
And I log in to a new session 12.552
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.661
And I plug USB drive "to_upgrade" 2.193
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.634
Then the running Tails is installed on USB drive "to_upgrade" 17.920
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.160
After features/support/hooks.rb:339 1.706
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.083
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.946
Then all tps features from the old Tails version are active 1.032
And Tails is running from USB drive "to_upgrade" 0.199
And the boot device has safe access rights 1.769
And the expected persistent files created with the old Tails version are present in the filesystem 1.097
And all persistent directories from the old Tails version have safe access rights 1.960
After features/support/hooks.rb:339 0.545
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:34.075
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 8.354
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
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.185
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.265
When the network is plugged 0.025
And Tor is ready 11.831
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.582
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.375
Given I shutdown Tails and wait for the computer to power off 5.250
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.039
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.365
And the file system changes introduced in version 6.2~testoverlayfs are present 0.242
And only the 6.2~testoverlayfs SquashFS delta is installed 0.035
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.102
# 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.158
When the network is plugged 0.029
And Tor is ready 10.335
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.182
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.328
Given I shutdown Tails and wait for the computer to power off 3.820
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.361
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.951
And the file system changes introduced in version 6.3~testoverlayfs are present 0.342
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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.148
When the network is plugged 0.022
And Tor is ready 12.145
Then the Upgrader considers the system as up-to-date 0.127
# 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.518
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.309
After features/support/hooks.rb:339 0.738
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
20.129
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.687
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 8.572
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.535
After features/support/hooks.rb:339 0.634
After features/support/hooks.rb:108 0.000