Project Number Date
test_Tails_ISO_stable 6307 18 Apr 2026, 11:19

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:22.412 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
58.424
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.248
When I start Tails from USB drive "old" with network unplugged 40.813
Then the boot device has safe access rights 2.517
And Tails is running from USB drive "old" 0.240
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 1.243
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.097
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 51.590
Then Tails is running from USB drive "old" 0.250
And I create a persistent partition 24.155
And I take note of which tps features are available 0.583
Then a Tails persistence partition exists on USB drive "old" 0.581
And I shutdown Tails and wait for the computer to power off 7.874
After features/support/hooks.rb:331 0.217
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.148
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.063
Then Tails is running from USB drive "old" 0.235
And all tps features are active 1.086
When I write some files expected to persist 1.226
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.175
And all persistence configuration files have safe access rights 0.438
And all persistent directories from the old Tails version have safe access rights 1.968
And I take note of which tps features are available 0.172
And I shutdown Tails and wait for the computer to power off 8.027
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.704
After features/support/hooks.rb:331 0.218
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.553
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 7.756
And I log in to a new session 11.386
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.687
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.213
Then the running Tails is installed on USB drive "to_upgrade" 15.022
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 3.576
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.892
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.046
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.309
Then all tps features from the old Tails version are active 0.951
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 2.400
And the expected persistent files created with the old Tails version are present in the filesystem 1.117
And all persistent directories from the old Tails version have safe access rights 1.850
After features/support/hooks.rb:331 0.789
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
4:56.110
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 8.236
And no SquashFS delta is installed 0.060
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.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.328
When the network is plugged 0.015
And Tor is ready 43.174
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.356
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.905
Given I shutdown Tails and wait for the computer to power off 19.765
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.337
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.098
And the file system changes introduced in version 6.2~testoverlayfs are present 0.224
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.214
When the network is plugged 0.016
And Tor is ready 21.936
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.356
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.281
Given I shutdown Tails and wait for the computer to power off 18.419
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.323
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.061
And the file system changes introduced in version 6.3~testoverlayfs are present 0.303
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.194
When the network is plugged 0.016
And Tor is ready 21.063
Then the Upgrader considers the system as up-to-date 0.100
# 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.098
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.326
After features/support/hooks.rb:331 0.865
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
24.184
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.597
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.039
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 15.881
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.385
After features/support/hooks.rb:331 1.030
After features/support/hooks.rb:100 0.000