Project Number Date
test_Tails_ISO_21603-fragnesia 2 14 May 2026, 19:35

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:2.394 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:17.961
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.623
When I start Tails from USB drive "old" with network unplugged 58.871
Then the boot device has safe access rights 3.508
And Tails is running from USB drive "old" 0.279
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.239
And I unplug USB drive "old" 0.227
After features/support/hooks.rb:335 3.699
After features/support/hooks.rb:104 0.007
Tags: @product
1:32.747
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 56.926
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 25.879
And I take note of which tps features are available 0.357
Then a Tails persistence partition exists on USB drive "old" 0.575
And I shutdown Tails and wait for the computer to power off 8.639
After features/support/hooks.rb:335 0.667
After features/support/hooks.rb:104 0.007
Tags: @product
1:27.597
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.432
Then Tails is running from USB drive "old" 0.238
And all tps features are active 1.069
When I write some files expected to persist 1.283
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 1.925
And I take note of which tps features are available 0.184
And I shutdown Tails and wait for the computer to power off 4.088
# 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" 12.818
After features/support/hooks.rb:335 0.235
After features/support/hooks.rb:104 0.007
Tags: @product
2:13.341
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.010
And I log in to a new session 13.612
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.700
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.070
Then the running Tails is installed on USB drive "to_upgrade" 16.395
And I unplug USB drive "to_upgrade" 0.166
And I unplug USB drive "__internal" 0.169
After features/support/hooks.rb:335 4.136
After features/support/hooks.rb:104 0.000
Tags: @product
1:16.457
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.116
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.005
Then all tps features from the old Tails version are active 1.065
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 3.462
And the expected persistent files created with the old Tails version are present in the filesystem 1.353
And all persistent directories from the old Tails version have safe access rights 2.225
After features/support/hooks.rb:335 0.825
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:51.262
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.810
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.377
When the network is plugged 0.015
And Tor is ready 13.294
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.439
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.602
Given I shutdown Tails and wait for the computer to power off 9.769
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.404
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.245
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.177
# 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.282
When the network is plugged 0.013
And Tor is ready 11.748
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.708
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.944
Given I shutdown Tails and wait for the computer to power off 8.360
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.083
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.030
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.052
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.016
And Tor is ready 10.906
Then the Upgrader considers the system as up-to-date 10.523
# 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 4.465
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.369
After features/support/hooks.rb:335 0.788
After features/support/hooks.rb:104 0.021
Tags: @product @automatic_upgrade
23.026
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.876
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 10.131
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.621
After features/support/hooks.rb:335 0.724
After features/support/hooks.rb:104 0.000