Project Number Date
test_Tails_ISO_stable 6255 01 Apr 2026, 17:48

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:23.024 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:12.976
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 14.518
When I start Tails from USB drive "old" with network unplugged 52.947
Then the boot device has safe access rights 3.486
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.161
After features/support/hooks.rb:331 3.872
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.899
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login 55.776
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 25.418
And I take note of which tps features are available 0.901
Then a Tails persistence partition exists on USB drive "old" 0.783
And I shutdown Tails and wait for the computer to power off 8.406
After features/support/hooks.rb:331 0.543
After features/support/hooks.rb:100 0.013
Tags: @product
1:31.666
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.770
Then Tails is running from USB drive "old" 0.343
And all tps features are active 1.308
When I write some files expected to persist 1.564
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.484
And all persistent directories from the old Tails version have safe access rights 2.092
And I take note of which tps features are available 0.159
And I shutdown Tails and wait for the computer to power off 8.146
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.396
After features/support/hooks.rb:331 0.237
After features/support/hooks.rb:100 0.007
Tags: @product
2:15.980
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 8.722
And I log in to a new session 14.487
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.873
And I plug USB drive "to_upgrade" 2.270
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.337
Then the running Tails is installed on USB drive "to_upgrade" 16.913
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.149
After features/support/hooks.rb:331 2.963
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.423
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.299
Then all tps features from the old Tails version are active 1.040
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.048
And the expected persistent files created with the old Tails version are present in the filesystem 1.176
And all persistent directories from the old Tails version have safe access rights 2.479
After features/support/hooks.rb:331 0.906
After features/support/hooks.rb:100 0.010
5:10.696
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.795
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.018
And Tor is ready 43.368
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.373
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.976
Given I shutdown Tails and wait for the computer to power off 19.359
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.029
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.202
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.215
When the network is plugged 0.014
And Tor is ready 22.035
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.402
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.740
Given I shutdown Tails and wait for the computer to power off 12.672
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.686
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.473
And the file system changes introduced in version 6.3~testoverlayfs are present 0.530
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.149
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.077
And Tor is ready 20.850
Then the Upgrader considers the system as up-to-date 0.107
# 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.356
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.436
After features/support/hooks.rb:331 0.841
After features/support/hooks.rb:100 0.019
26.381
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.808
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
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.023
And Tor is ready 17.823
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.383
After features/support/hooks.rb:331 0.947
After features/support/hooks.rb:100 0.000