Project Number Date
test_Tails_ISO_stable 6351 05 May 2026, 11:29

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:21.740 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.065
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.934
When I start Tails from USB drive "old" with network unplugged 1:0.169
Then the boot device has safe access rights 3.086
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.159
After features/support/hooks.rb:331 3.588
After features/support/hooks.rb:100 0.032
Tags: @product
1:34.878
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login 59.784
Then Tails is running from USB drive "old" 0.292
And I create a persistent partition 26.020
And I take note of which tps features are available 0.832
Then a Tails persistence partition exists on USB drive "old" 0.728
And I shutdown Tails and wait for the computer to power off 7.155
After features/support/hooks.rb:331 0.528
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.644
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.029
Then Tails is running from USB drive "old" 0.288
And all tps features are active 1.381
When I write some files expected to persist 1.386
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.619
And all persistent directories from the old Tails version have safe access rights 2.460
And I take note of which tps features are available 0.186
And I shutdown Tails and wait for the computer to power off 4.343
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.617
After features/support/hooks.rb:331 0.254
After features/support/hooks.rb:100 0.008
Tags: @product
2:17.310
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 without a persistent partition and stopped at Tails Greeter's login screen 8.378
And I log in to a new session 13.885
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.395
And I plug USB drive "to_upgrade" 2.269
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.615
Then the running Tails is installed on USB drive "to_upgrade" 18.453
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.161
After features/support/hooks.rb:331 2.073
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.281
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.902
Then all tps features from the old Tails version are active 1.334
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.231
And the expected persistent files created with the old Tails version are present in the filesystem 1.200
And all persistent directories from the old Tails version have safe access rights 2.216
After features/support/hooks.rb:331 0.985
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:54.382
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 9.003
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
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.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.024
And Tor is ready 23.762
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.415
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.262
Given I shutdown Tails and wait for the computer to power off 19.665
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.172
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.226
And the file system changes introduced in version 6.2~testoverlayfs are present 0.250
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.236
When the network is plugged 0.014
And Tor is ready 22.498
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.410
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.764
Given I shutdown Tails and wait for the computer to power off 17.678
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.969
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.206
And the file system changes introduced in version 6.3~testoverlayfs are present 0.414
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.033
And Tor is ready 21.996
Then the Upgrader considers the system as up-to-date 0.130
# 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.084
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.391
After features/support/hooks.rb:331 0.717
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
27.177
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.380
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 18.845
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.394
After features/support/hooks.rb:331 0.847
After features/support/hooks.rb:100 0.000