Project Number Date
test_Tails_ISO_devel 4425 01 Jun 2026, 17:32

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:44.219 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:11.986
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.836
When I start Tails from USB drive "old" with network unplugged 52.792
Then the boot device has safe access rights 3.220
And Tails is running from USB drive "old" 0.387
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.271
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:335 3.660
After features/support/hooks.rb:104 0.009
Tags: @product
1:32.419
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.020
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 58.181
Then Tails is running from USB drive "old" 0.283
And I create a persistent partition 24.719
And I take note of which tps features are available 0.320
Then a Tails persistence partition exists on USB drive "old" 0.591
And I shutdown Tails and wait for the computer to power off 8.233
After features/support/hooks.rb:335 0.450
After features/support/hooks.rb:104 0.007
Tags: @product
1:28.741
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.375
Then Tails is running from USB drive "old" 0.256
And all tps features are active 1.214
When I write some files expected to persist 1.399
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.327
And all persistent directories from the old Tails version have safe access rights 1.977
And I take note of which tps features are available 0.208
And I shutdown Tails and wait for the computer to power off 8.060
# 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.587
After features/support/hooks.rb:335 0.619
After features/support/hooks.rb:104 0.007
Tags: @product
2:13.321
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.658
And I log in to a new session 14.495
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.747
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.855
Then the running Tails is installed on USB drive "to_upgrade" 15.005
And I unplug USB drive "to_upgrade" 0.161
And I unplug USB drive "__internal" 0.161
After features/support/hooks.rb:335 2.690
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.864
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.567
Then all tps features from the old Tails version are active 1.110
And Tails is running from USB drive "to_upgrade" 0.259
And the boot device has safe access rights 2.761
And the expected persistent files created with the old Tails version are present in the filesystem 1.195
And all persistent directories from the old Tails version have safe access rights 1.895
After features/support/hooks.rb:335 0.929
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:47.481
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.227
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.217
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.339
When the network is plugged 0.050
And Tor is ready 12.555
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.660
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.327
Given I shutdown Tails and wait for the computer to power off 9.619
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.886
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.524
And the file system changes introduced in version 6.2~testoverlayfs are present 0.233
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.194
When the network is plugged 0.016
And Tor is ready 12.452
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.666
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.975
Given I shutdown Tails and wait for the computer to power off 8.397
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.646
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.123
And the file system changes introduced in version 6.3~testoverlayfs are present 0.362
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.016
And Tor is ready 11.328
Then the Upgrader considers the system as up-to-date 10.491
# 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.696
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.408
After features/support/hooks.rb:335 1.044
After features/support/hooks.rb:104 0.049
Tags: @product @automatic_upgrade
19.404
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 7.566
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.545
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.942
After features/support/hooks.rb:335 0.821
After features/support/hooks.rb:104 0.000