Project Number Date
test_Tails_ISO_stable 6159 22 Feb 2026, 11:31

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 11:57.670 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:7.522
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 12.961
When I start Tails from USB drive "old" with network unplugged 50.071
Then the boot device has safe access rights 2.720
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.204
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:331 1.564
After features/support/hooks.rb:100 0.006
Tags: @product
1:19.337
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 50.364
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 23.149
And I take note of which tps features are available 0.675
Then a Tails persistence partition exists on USB drive "old" 0.567
And I shutdown Tails and wait for the computer to power off 4.290
After features/support/hooks.rb:331 0.512
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.206
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.948
Then Tails is running from USB drive "old" 0.254
And all tps features are active 1.062
When I write some files expected to persist 1.222
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.294
And all persistent directories from the old Tails version have safe access rights 1.655
And I take note of which tps features are available 0.139
And I shutdown Tails and wait for the computer to power off 7.867
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.544
After features/support/hooks.rb:331 0.151
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.941
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.438
And I log in to a new session 10.807
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.692
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.127
Then the running Tails is installed on USB drive "to_upgrade" 15.394
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:331 2.636
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.991
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.046
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.376
Then all tps features from the old Tails version are active 0.978
And Tails is running from USB drive "to_upgrade" 0.260
And the boot device has safe access rights 2.419
And the expected persistent files created with the old Tails version are present in the filesystem 1.093
And all persistent directories from the old Tails version have safe access rights 1.815
After features/support/hooks.rb:331 0.732
After features/support/hooks.rb:100 0.022
4:26.789
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.100
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.367
When the network is plugged 0.015
And Tor is ready 19.279
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.349
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.367
Given I shutdown Tails and wait for the computer to power off 19.813
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.606
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.019
And the file system changes introduced in version 6.2~testoverlayfs are present 0.186
And only the 6.2~testoverlayfs SquashFS delta is installed 0.035
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.327
When the network is plugged 0.015
And Tor is ready 20.162
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.361
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.800
Given I shutdown Tails and wait for the computer to power off 17.031
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.013
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.025
And the file system changes introduced in version 6.3~testoverlayfs are present 0.367
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.013
And Tor is ready 21.599
Then the Upgrader considers the system as up-to-date 0.103
# 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.257
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.447
After features/support/hooks.rb:331 0.691
After features/support/hooks.rb:100 0.010
24.882
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.461
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 16.726
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.358
After features/support/hooks.rb:331 0.887
After features/support/hooks.rb:100 0.000