Project Number Date
test_Tails_ISO_21641-update-moat-frontends 2 13 Aug 2026, 16:05

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:41.046 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.994
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.113
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.617
When I start Tails from USB drive "old" with network unplugged 55.208
Then the boot device has safe access rights 2.286
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.229
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 3.732
After features/support/hooks.rb:108 0.005
Tags: @product
1:25.464
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 49.965
Then Tails is running from USB drive "old" 0.202
And I create a persistent partition 23.289
And I take note of which tps features are available 7.327
Then a Tails persistence partition exists on USB drive "old" 0.543
And I shutdown Tails and wait for the computer to power off 4.044
After features/support/hooks.rb:339 0.392
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.458
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.776
Then Tails is running from USB drive "old" 0.332
And all tps features are active 7.937
When I write some files expected to persist 1.365
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.161
And all persistence configuration files have safe access rights 0.268
And all persistent directories from the old Tails version have safe access rights 1.677
And I take note of which tps features are available 6.079
And I shutdown Tails and wait for the computer to power off 5.345
# 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.414
After features/support/hooks.rb:339 0.380
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.952
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.334
And I log in to a new session 11.934
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.580
And I plug USB drive "to_upgrade" 2.284
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.494
Then the running Tails is installed on USB drive "to_upgrade" 18.074
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 1.661
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.117
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.206
Then all tps features from the old Tails version are active 1.025
And Tails is running from USB drive "to_upgrade" 0.175
And the boot device has safe access rights 2.001
And the expected persistent files created with the old Tails version are present in the filesystem 1.000
And all persistent directories from the old Tails version have safe access rights 1.614
After features/support/hooks.rb:339 0.554
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:48.352
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.034
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.169
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.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.252
When the network is plugged 0.026
And Tor is ready 20.702
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.575
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.427
Given I shutdown Tails and wait for the computer to power off 5.285
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.254
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.094
And the file system changes introduced in version 6.2~testoverlayfs are present 0.180
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.168
When the network is plugged 0.024
And Tor is ready 20.960
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.304
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.999
Given I shutdown Tails and wait for the computer to power off 4.150
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.133
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.718
And the file system changes introduced in version 6.3~testoverlayfs are present 0.318
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.084
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.030
And Tor is ready 10.483
Then the Upgrader considers the system as up-to-date 0.139
# 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.629
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.387
After features/support/hooks.rb:339 1.000
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
19.705
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.799
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
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.034
And Tor is ready 10.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.580
After features/support/hooks.rb:339 0.965
After features/support/hooks.rb:108 0.000