Project Number Date
test_Tails_ISO_stable 6235 25 Mar 2026, 15:17

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.918 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.523
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.064
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.588
When I start Tails from USB drive "old" with network unplugged 52.055
Then the boot device has safe access rights 3.052
And Tails is running from USB drive "old" 0.259
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.223
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 3.629
After features/support/hooks.rb:100 0.030
Tags: @product
1:34.830
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 58.644
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 26.122
And I take note of which tps features are available 0.923
Then a Tails persistence partition exists on USB drive "old" 0.616
And I shutdown Tails and wait for the computer to power off 8.101
After features/support/hooks.rb:331 0.607
After features/support/hooks.rb:100 0.007
Tags: @product
1:32.414
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.921
Then Tails is running from USB drive "old" 0.312
And all tps features are active 1.253
When I write some files expected to persist 1.544
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.588
And all persistent directories from the old Tails version have safe access rights 2.218
And I take note of which tps features are available 0.211
And I shutdown Tails and wait for the computer to power off 4.121
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.921
After features/support/hooks.rb:331 0.496
After features/support/hooks.rb:100 0.008
Tags: @product
2:18.221
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.556
And I log in to a new session 15.371
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.080
And I plug USB drive "to_upgrade" 2.273
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.262
Then the running Tails is installed on USB drive "to_upgrade" 17.346
And I unplug USB drive "to_upgrade" 0.160
And I unplug USB drive "__internal" 0.170
After features/support/hooks.rb:331 2.582
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.413
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.611
Then all tps features from the old Tails version are active 1.206
And Tails is running from USB drive "to_upgrade" 0.518
And the boot device has safe access rights 2.927
And the expected persistent files created with the old Tails version are present in the filesystem 1.457
And all persistent directories from the old Tails version have safe access rights 2.600
After features/support/hooks.rb:331 0.893
After features/support/hooks.rb:100 0.009
4:58.573
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.787
And no SquashFS delta is installed 0.139
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
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.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.374
When the network is plugged 0.017
And Tor is ready 22.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.483
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.451
Given I shutdown Tails and wait for the computer to power off 19.704
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.179
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.292
And the file system changes introduced in version 6.2~testoverlayfs are present 0.276
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.198
When the network is plugged 0.021
And Tor is ready 21.799
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.380
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.682
Given I shutdown Tails and wait for the computer to power off 18.307
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.551
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.301
And the file system changes introduced in version 6.3~testoverlayfs are present 0.455
And only the 6.3~testoverlayfs SquashFS delta is installed 0.099
# 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.190
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.015
And Tor is ready 22.142
Then the Upgrader considers the system as up-to-date 0.117
# 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.550
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.444
After features/support/hooks.rb:331 1.005
After features/support/hooks.rb:100 0.014
26.940
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.219
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.087
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 17.898
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.450
After features/support/hooks.rb:331 1.087
After features/support/hooks.rb:100 0.000