Project Number Date
test_Tails_ISO_stable 6138 10 Feb 2026, 22:09

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 15:0.954 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:28.635
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.168
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 32.752
When I start Tails from USB drive "old" with network unplugged 50.060
Then the boot device has safe access rights 3.651
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:331 3.751
After features/support/hooks.rb:100 0.009
Tags: @product
1:45.041
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:5.559
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 29.217
And I take note of which tps features are available 1.246
Then a Tails persistence partition exists on USB drive "old" 0.663
And I shutdown Tails and wait for the computer to power off 7.863
After features/support/hooks.rb:331 0.517
After features/support/hooks.rb:100 0.011
Tags: @product
2:12.166
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:16.215
Then Tails is running from USB drive "old" 0.715
And all tps features are active 4.299
When I write some files expected to persist 1.555
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.330
And all persistent directories from the old Tails version have safe access rights 2.648
And I take note of which tps features are available 19.523
And I shutdown Tails and wait for the computer to power off 7.769
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.698
After features/support/hooks.rb:331 0.339
After features/support/hooks.rb:100 0.020
Tags: @product
2:53.707
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.222
And I log in to a new session 14.978
And I clone USB drive "old" to a new USB drive "to_upgrade" 5.344
And I plug USB drive "to_upgrade" 2.423
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:58.538
Then the running Tails is installed on USB drive "to_upgrade" 19.731
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.235
After features/support/hooks.rb:331 2.094
After features/support/hooks.rb:100 0.000
Tags: @product
1:25.334
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:16.487
Then all tps features from the old Tails version are active 1.475
And Tails is running from USB drive "to_upgrade" 0.281
And the boot device has safe access rights 3.158
And the expected persistent files created with the old Tails version are present in the filesystem 1.434
And all persistent directories from the old Tails version have safe access rights 2.327
After features/support/hooks.rb:331 1.027
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:25.099
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 11.935
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.392
When the network is plugged 0.056
And Tor is ready 14.063
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.786
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.634
Given I shutdown Tails and wait for the computer to power off 12.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.065
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 1.987
And the file system changes introduced in version 6.2~testoverlayfs are present 0.278
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.266
When the network is plugged 0.056
And Tor is ready 12.043
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.713
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.610
Given I shutdown Tails and wait for the computer to power off 9.748
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.001
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.967
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.074
And Tor is ready 11.806
Then the Upgrader considers the system as up-to-date 0.129
# 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.429
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.533
After features/support/hooks.rb:331 1.021
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
50.971
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 10.301
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 39.643
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.614
After features/support/hooks.rb:331 1.192
After features/support/hooks.rb:100 0.000