Project Number Date
test_Tails_ISO_devel 4439 09 Jun 2026, 11: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 10:58.953 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.753
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 12.778
When I start Tails from USB drive "old" with network unplugged 54.621
Then the boot device has safe access rights 2.614
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:335 1.408
After features/support/hooks.rb:104 0.006
Tags: @product
1:21.797
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 51.789
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 24.547
And I take note of which tps features are available 0.316
Then a Tails persistence partition exists on USB drive "old" 0.568
And I shutdown Tails and wait for the computer to power off 4.296
After features/support/hooks.rb:335 0.530
After features/support/hooks.rb:104 0.007
Tags: @product
1:20.420
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.193
Then Tails is running from USB drive "old" 0.263
And all tps features are active 1.093
When I write some files expected to persist 1.272
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.170
And all persistence configuration files have safe access rights 0.321
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.144
And I shutdown Tails and wait for the computer to power off 4.074
# 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.773
After features/support/hooks.rb:335 0.400
After features/support/hooks.rb:104 0.007
Tags: @product
2:9.866
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.309
And I log in to a new session 11.930
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.799
And I plug USB drive "to_upgrade" 2.238
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.429
Then the running Tails is installed on USB drive "to_upgrade" 14.848
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:335 2.204
After features/support/hooks.rb:104 0.000
Tags: @product
1:5.703
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.119
Then all tps features from the old Tails version are active 0.962
And Tails is running from USB drive "to_upgrade" 0.247
And the boot device has safe access rights 2.358
And the expected persistent files created with the old Tails version are present in the filesystem 1.105
And all persistent directories from the old Tails version have safe access rights 1.860
After features/support/hooks.rb:335 0.533
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:29.972
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 with a persistent partition enabled and logged in 8.074
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.340
When the network is plugged 0.016
And Tor is ready 13.108
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.088
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.033
Given I shutdown Tails and wait for the computer to power off 9.312
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.592
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.109
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.199
When the network is plugged 0.018
And Tor is ready 9.617
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.749
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.874
Given I shutdown Tails and wait for the computer to power off 4.003
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.780
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.169
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.201
When the network is plugged 0.017
And Tor is ready 10.425
Then the Upgrader considers the system as up-to-date 10.532
# 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.746
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.354
After features/support/hooks.rb:335 0.920
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
19.437
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 with a persistent partition enabled and logged in 7.280
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 9.534
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.226
After features/support/hooks.rb:335 0.799
After features/support/hooks.rb:104 0.000