Project Number Date
test_Tails_ISO_devel 4377 05 May 2026, 13:58

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 13:18.045 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:20.499
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.607
When I start Tails from USB drive "old" with network unplugged 1:1.434
Then the boot device has safe access rights 2.668
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:331 1.358
After features/support/hooks.rb:100 0.006
Tags: @product
1:33.318
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 57.883
Then Tails is running from USB drive "old" 0.279
And I create a persistent partition 26.397
And I take note of which tps features are available 0.735
Then a Tails persistence partition exists on USB drive "old" 1.040
And I shutdown Tails and wait for the computer to power off 6.921
After features/support/hooks.rb:331 0.153
After features/support/hooks.rb:100 0.006
Tags: @product
1:30.721
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.276
Then Tails is running from USB drive "old" 0.261
And all tps features are active 1.248
When I write some files expected to persist 1.369
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.456
And all persistent directories from the old Tails version have safe access rights 1.969
And I take note of which tps features are available 0.173
And I shutdown Tails and wait for the computer to power off 7.361
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.331
After features/support/hooks.rb:331 0.587
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.483
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.030
And I log in to a new session 14.309
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.815
And I plug USB drive "to_upgrade" 2.340
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.335
Then the running Tails is installed on USB drive "to_upgrade" 17.327
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:331 2.174
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.487
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.784
Then all tps features from the old Tails version are active 1.131
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.907
And the expected persistent files created with the old Tails version are present in the filesystem 1.228
And all persistent directories from the old Tails version have safe access rights 2.117
After features/support/hooks.rb:331 0.749
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:54.812
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.518
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
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.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.408
When the network is plugged 0.022
And Tor is ready 21.928
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.459
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.185
Given I shutdown Tails and wait for the computer to power off 20.460
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.969
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.216
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.238
When the network is plugged 0.016
And Tor is ready 23.687
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.424
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.018
Given I shutdown Tails and wait for the computer to power off 18.025
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.435
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.243
And the file system changes introduced in version 6.3~testoverlayfs are present 0.410
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.136
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 22.460
Then the Upgrader considers the system as up-to-date 0.098
# 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 5.435
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.509
After features/support/hooks.rb:331 0.675
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
28.722
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.694
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 20.307
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.375
After features/support/hooks.rb:331 1.057
After features/support/hooks.rb:100 0.000