Project Number Date
test_Tails_ISO_devel 4404 19 May 2026, 18:45

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:20.666 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:1.131
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.776
When I start Tails from USB drive "old" with network unplugged 42.821
Then the boot device has safe access rights 2.740
And Tails is running from USB drive "old" 0.247
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:335 3.484
After features/support/hooks.rb:104 0.006
Tags: @product
1:28.848
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 54.385
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 24.995
And I take note of which tps features are available 0.336
Then a Tails persistence partition exists on USB drive "old" 0.552
And I shutdown Tails and wait for the computer to power off 8.255
After features/support/hooks.rb:335 0.498
After features/support/hooks.rb:104 0.006
Tags: @product
1:25.114
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.801
Then Tails is running from USB drive "old" 0.262
And all tps features are active 1.273
When I write some files expected to persist 1.387
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 2.060
And I take note of which tps features are available 0.165
And I shutdown Tails and wait for the computer to power off 4.159
# 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.334
After features/support/hooks.rb:335 0.257
After features/support/hooks.rb:104 0.007
Tags: @product
2:13.331
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.253
And I log in to a new session 13.205
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.793
And I plug USB drive "to_upgrade" 2.279
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.468
Then the running Tails is installed on USB drive "to_upgrade" 17.055
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:335 2.603
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.173
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:3.028
Then all tps features from the old Tails version are active 1.046
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 2.623
And the expected persistent files created with the old Tails version are present in the filesystem 1.122
And all persistent directories from the old Tails version have safe access rights 2.003
After features/support/hooks.rb:335 0.563
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:41.063
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 with a persistent partition enabled and logged in 8.438
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.239
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.371
When the network is plugged 0.018
And Tor is ready 13.058
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.240
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.191
Given I shutdown Tails and wait for the computer to power off 10.683
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.876
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.116
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.114
# 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.187
When the network is plugged 0.016
And Tor is ready 10.633
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.956
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.611
Given I shutdown Tails and wait for the computer to power off 8.154
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.860
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.253
And the file system changes introduced in version 6.3~testoverlayfs are present 0.363
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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.020
And Tor is ready 10.222
Then the Upgrader considers the system as up-to-date 10.569
# 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.355
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.412
After features/support/hooks.rb:335 1.017
After features/support/hooks.rb:104 0.014
Tags: @product @automatic_upgrade
21.003
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 7.618
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.754
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.305
After features/support/hooks.rb:335 0.766
After features/support/hooks.rb:104 0.000