Project Number Date
test_Tails_ISO_stable 6081 20 Jan 2026, 12:02

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:12.848 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:51.174
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.045
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.543
When I start Tails from USB drive "old" with network unplugged 1:33.338
Then the boot device has safe access rights 2.565
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:331 3.808
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.835
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 52.291
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 24.130
And I take note of which tps features are available 0.720
Then a Tails persistence partition exists on USB drive "old" 0.543
And I shutdown Tails and wait for the computer to power off 7.865
After features/support/hooks.rb:331 0.554
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.067
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.437
Then Tails is running from USB drive "old" 0.230
And all tps features are active 1.037
When I write some files expected to persist 1.127
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.278
And all persistent directories from the old Tails version have safe access rights 1.755
And I take note of which tps features are available 0.163
And I shutdown Tails and wait for the computer to power off 7.809
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.025
After features/support/hooks.rb:331 0.227
After features/support/hooks.rb:100 0.006
Tags: @product
2:17.576
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 without a persistent partition and stopped at Tails Greeter's login screen 8.148
And I log in to a new session 11.897
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.760
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.686
Then the running Tails is installed on USB drive "to_upgrade" 15.613
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 9.836
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.545
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.922
Then all tps features from the old Tails version are active 0.993
And Tails is running from USB drive "to_upgrade" 0.240
And the boot device has safe access rights 2.458
And the expected persistent files created with the old Tails version are present in the filesystem 0.999
And all persistent directories from the old Tails version have safe access rights 1.885
After features/support/hooks.rb:331 0.660
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
3:47.851
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.608
And no SquashFS delta is installed 0.171
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.337
When the network is plugged 0.019
And Tor is ready 13.972
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.975
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.222
Given I shutdown Tails and wait for the computer to power off 13.944
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.372
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 0.993
And the file system changes introduced in version 6.2~testoverlayfs are present 0.266
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.165
When the network is plugged 0.013
And Tor is ready 10.696
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.295
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.362
Given I shutdown Tails and wait for the computer to power off 8.128
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.505
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.030
And the file system changes introduced in version 6.3~testoverlayfs are present 0.316
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.012
And Tor is ready 9.761
Then the Upgrader considers the system as up-to-date 10.500
# 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 3.700
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:331 0.724
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
20.796
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.519
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.969
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.986
After features/support/hooks.rb:331 0.945
After features/support/hooks.rb:100 0.000