Project Number Date
test_Tails_ISO_stable 6168 25 Feb 2026, 11:37

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 12:41.252 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:18.513
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.123
When I start Tails from USB drive "old" with network unplugged 59.825
Then the boot device has safe access rights 2.713
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:331 1.575
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.664
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 54.850
Then Tails is running from USB drive "old" 0.253
And I create a persistent partition 25.498
And I take note of which tps features are available 1.016
Then a Tails persistence partition exists on USB drive "old" 0.691
And I shutdown Tails and wait for the computer to power off 8.277
After features/support/hooks.rb:331 0.198
After features/support/hooks.rb:100 0.006
Tags: @product
1:22.258
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.966
Then Tails is running from USB drive "old" 0.234
And all tps features are active 1.021
When I write some files expected to persist 1.227
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 1.964
And I take note of which tps features are available 0.152
And I shutdown Tails and wait for the computer to power off 2.741
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.370
After features/support/hooks.rb:331 0.571
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.502
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.621
And I log in to a new session 10.374
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.814
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.356
Then the running Tails is installed on USB drive "to_upgrade" 16.753
And I unplug USB drive "to_upgrade" 0.151
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:331 2.691
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.473
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.626
Then all tps features from the old Tails version are active 0.956
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.446
And the expected persistent files created with the old Tails version are present in the filesystem 1.206
And all persistent directories from the old Tails version have safe access rights 1.936
After features/support/hooks.rb:331 0.795
After features/support/hooks.rb:100 0.008
4:39.982
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 with a persistent partition enabled and logged in 8.825
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.392
When the network is plugged 0.015
And Tor is ready 21.618
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.363
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.707
Given I shutdown Tails and wait for the computer to power off 18.760
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.588
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.131
And the file system changes introduced in version 6.2~testoverlayfs are present 0.235
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.242
When the network is plugged 0.016
And Tor is ready 20.923
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.381
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.298
Given I shutdown Tails and wait for the computer to power off 17.368
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.305
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.175
And the file system changes introduced in version 6.3~testoverlayfs are present 0.353
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.194
When the network is plugged 0.014
And Tor is ready 22.292
Then the Upgrader considers the system as up-to-date 0.120
# 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.280
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.413
After features/support/hooks.rb:331 1.293
After features/support/hooks.rb:100 0.044
26.858
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.034
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.800
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 18.324
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.387
After features/support/hooks.rb:331 0.891
After features/support/hooks.rb:100 0.000