Project Number Date
test_Tails_ISO_stable 6494 09 Jul 2026, 11:44

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:33.974 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:3.723
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.047
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.153
When I start Tails from USB drive "old" with network unplugged 46.315
Then the boot device has safe access rights 2.535
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:339 3.405
After features/support/hooks.rb:108 0.018
Tags: @product
1:27.849
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 51.624
Then Tails is running from USB drive "old" 0.200
And I create a persistent partition 23.506
And I take note of which tps features are available 3.707
Then a Tails persistence partition exists on USB drive "old" 0.526
And I shutdown Tails and wait for the computer to power off 8.202
After features/support/hooks.rb:339 0.563
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.173
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.267
Then Tails is running from USB drive "old" 0.234
And all tps features are active 4.711
When I write some files expected to persist 1.263
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.300
And all persistent directories from the old Tails version have safe access rights 1.821
And I take note of which tps features are available 3.710
And I shutdown Tails and wait for the computer to power off 7.927
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.733
After features/support/hooks.rb:339 0.188
After features/support/hooks.rb:108 0.005
Tags: @product
2:8.558
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.150
And I log in to a new session 11.481
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.766
And I plug USB drive "to_upgrade" 2.200
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.490
Then the running Tails is installed on USB drive "to_upgrade" 14.199
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 1.969
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.050
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.045
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.561
Then all tps features from the old Tails version are active 0.875
And Tails is running from USB drive "to_upgrade" 0.248
And the boot device has safe access rights 2.388
And the expected persistent files created with the old Tails version are present in the filesystem 1.085
And all persistent directories from the old Tails version have safe access rights 1.845
After features/support/hooks.rb:339 0.683
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:46.947
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.273
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
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.375
When the network is plugged 0.016
And Tor is ready 12.347
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.532
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.501
Given I shutdown Tails and wait for the computer to power off 6.879
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.902
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.807
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.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.203
When the network is plugged 0.015
And Tor is ready 10.573
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.535
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.410
Given I shutdown Tails and wait for the computer to power off 7.865
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.565
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 4.713
And the file system changes introduced in version 6.3~testoverlayfs are present 0.329
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.173
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.232
When the network is plugged 0.013
And Tor is ready 10.617
Then the Upgrader considers the system as up-to-date 10.536
# 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.148
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.348
After features/support/hooks.rb:339 0.977
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
21.670
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.313
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
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.016
And Tor is ready 10.927
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.108
After features/support/hooks.rb:339 0.523
After features/support/hooks.rb:108 0.000