Project Number Date
test_Tails_ISO_21641-update-moat-frontends 1 13 Aug 2026, 15:22

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:43.693 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:12.906
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.679
When I start Tails from USB drive "old" with network unplugged 54.741
Then the boot device has safe access rights 2.712
And Tails is running from USB drive "old" 0.204
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.202
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 1.237
After features/support/hooks.rb:108 0.012
Tags: @product
1:26.688
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.118
And I start Tails from USB drive "old" with network unplugged and I login 50.482
Then Tails is running from USB drive "old" 0.296
And I create a persistent partition 24.710
And I take note of which tps features are available 8.012
Then a Tails persistence partition exists on USB drive "old" 0.505
And I shutdown Tails and wait for the computer to power off 2.562
After features/support/hooks.rb:339 0.148
After features/support/hooks.rb:108 0.005
Tags: @product
1:37.376
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.037
Then Tails is running from USB drive "old" 0.230
And all tps features are active 8.521
When I write some files expected to persist 1.299
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.306
And all persistent directories from the old Tails version have safe access rights 1.747
And I take note of which tps features are available 6.028
And I shutdown Tails and wait for the computer to power off 4.360
# 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.596
After features/support/hooks.rb:339 0.428
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.438
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.717
And I log in to a new session 11.737
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.580
And I plug USB drive "to_upgrade" 2.292
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.637
Then the running Tails is installed on USB drive "to_upgrade" 18.122
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 1.754
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.240
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.112
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.851
Then all tps features from the old Tails version are active 0.972
And Tails is running from USB drive "to_upgrade" 0.209
And the boot device has safe access rights 2.115
And the expected persistent files created with the old Tails version are present in the filesystem 1.049
And all persistent directories from the old Tails version have safe access rights 1.929
After features/support/hooks.rb:339 0.984
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:44.340
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 8.856
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.366
When the network is plugged 0.028
And Tor is ready 11.923
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.365
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.506
Given I shutdown Tails and wait for the computer to power off 5.489
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.276
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.514
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.085
# 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.031
And Tor is ready 10.495
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.981
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.089
Given I shutdown Tails and wait for the computer to power off 4.143
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.222
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.417
And the file system changes introduced in version 6.3~testoverlayfs are present 0.289
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.080
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.176
When the network is plugged 0.027
And Tor is ready 10.205
Then the Upgrader considers the system as up-to-date 10.486
# 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.733
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.441
After features/support/hooks.rb:339 0.945
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
18.701
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.989
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 8.115
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.280
After features/support/hooks.rb:339 1.014
After features/support/hooks.rb:108 0.000