Project Number Date
test_Tails_ISO_stable 6585 17 Aug 2026, 17:37

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:34.044 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:5.782
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.011
When I start Tails from USB drive "old" with network unplugged 47.470
Then the boot device has safe access rights 2.376
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.079
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:339 3.780
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.690
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login 49.726
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 23.991
And I take note of which tps features are available 6.129
Then a Tails persistence partition exists on USB drive "old" 0.487
And I shutdown Tails and wait for the computer to power off 4.026
After features/support/hooks.rb:339 0.141
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.695
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.336
Then Tails is running from USB drive "old" 0.249
And all tps features are active 7.811
When I write some files expected to persist 1.060
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.133
And all persistence configuration files have safe access rights 0.308
And all persistent directories from the old Tails version have safe access rights 1.491
And I take note of which tps features are available 5.904
And I shutdown Tails and wait for the computer to power off 3.918
# 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.396
After features/support/hooks.rb:339 0.111
After features/support/hooks.rb:108 0.005
Tags: @product
2:16.313
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.555
And I log in to a new session 14.134
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.638
And I plug USB drive "to_upgrade" 2.308
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.486
Then the running Tails is installed on USB drive "to_upgrade" 18.956
And I unplug USB drive "to_upgrade" 0.107
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:339 1.832
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.017
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.320
Then all tps features from the old Tails version are active 1.165
And Tails is running from USB drive "to_upgrade" 0.226
And the boot device has safe access rights 2.479
And the expected persistent files created with the old Tails version are present in the filesystem 0.881
And all persistent directories from the old Tails version have safe access rights 1.855
After features/support/hooks.rb:339 0.650
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:38.832
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 8.945
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.028
And Tor is ready 13.375
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.952
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.186
Given I shutdown Tails and wait for the computer to power off 6.871
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.746
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 7.717
And the file system changes introduced in version 6.2~testoverlayfs are present 0.200
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.122
# 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.033
And Tor is ready 10.616
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.949
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.532
Given I shutdown Tails and wait for the computer to power off 3.996
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.183
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 8.667
And the file system changes introduced in version 6.3~testoverlayfs are present 0.444
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.116
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.045
And Tor is ready 11.651
Then the Upgrader considers the system as up-to-date 0.077
# 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.232
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.414
After features/support/hooks.rb:339 1.040
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
19.711
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.404
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 9.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.671
After features/support/hooks.rb:339 1.038
After features/support/hooks.rb:108 0.000