Project Number Date
test_Tails_ISO_21641-update-moat-frontends 3 13 Aug 2026, 17:12

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:53.623 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:14.621
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 15.000
When I start Tails from USB drive "old" with network unplugged 55.059
Then the boot device has safe access rights 2.712
And Tails is running from USB drive "old" 0.271
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 3.528
After features/support/hooks.rb:108 0.018
Tags: @product
1:27.529
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.111
And I start Tails from USB drive "old" with network unplugged and I login 52.082
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 23.845
And I take note of which tps features are available 6.517
Then a Tails persistence partition exists on USB drive "old" 0.511
And I shutdown Tails and wait for the computer to power off 4.104
After features/support/hooks.rb:339 0.382
After features/support/hooks.rb:108 0.005
Tags: @product
1:37.821
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.782
Then Tails is running from USB drive "old" 0.276
And all tps features are active 9.220
When I write some files expected to persist 1.115
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.281
And all persistent directories from the old Tails version have safe access rights 1.640
And I take note of which tps features are available 6.843
And I shutdown Tails and wait for the computer to power off 2.769
# 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.644
After features/support/hooks.rb:339 0.544
After features/support/hooks.rb:108 0.017
Tags: @product
2:16.594
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.519
And I log in to a new session 14.054
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.600
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.128
Then the running Tails is installed on USB drive "to_upgrade" 18.637
And I unplug USB drive "to_upgrade" 0.114
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 3.671
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.957
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.101
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.916
Then all tps features from the old Tails version are active 1.345
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.566
And the expected persistent files created with the old Tails version are present in the filesystem 1.039
And all persistent directories from the old Tails version have safe access rights 1.756
After features/support/hooks.rb:339 0.826
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:45.408
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.244
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.200
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.302
When the network is plugged 0.025
And Tor is ready 13.044
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.038
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.672
Given I shutdown Tails and wait for the computer to power off 5.753
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.710
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 9.305
And the file system changes introduced in version 6.2~testoverlayfs are present 0.206
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.107
# 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.165
When the network is plugged 0.026
And Tor is ready 11.019
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.931
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.502
Given I shutdown Tails and wait for the computer to power off 4.096
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.448
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.232
And the file system changes introduced in version 6.3~testoverlayfs are present 0.378
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.026
And Tor is ready 10.338
Then the Upgrader considers the system as up-to-date 10.430
# 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.099
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.328
After features/support/hooks.rb:339 0.957
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
19.691
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.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 8.623
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.603
After features/support/hooks.rb:339 0.977
After features/support/hooks.rb:108 0.000