Project Number Date
test_Tails_ISO_devel 4581 01 Sep 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 11:44.650 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:20.483
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.833
When I start Tails from USB drive "old" with network unplugged 1:2.240
Then the boot device has safe access rights 2.714
And Tails is running from USB drive "old" 0.193
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.032
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.624
After features/support/hooks.rb:108 0.009
Tags: @product
1:25.452
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login 48.834
Then Tails is running from USB drive "old" 0.204
And I create a persistent partition 24.799
And I take note of which tps features are available 6.877
Then a Tails persistence partition exists on USB drive "old" 0.555
And I shutdown Tails and wait for the computer to power off 4.069
After features/support/hooks.rb:339 0.398
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.255
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:3.729
Then Tails is running from USB drive "old" 0.268
And all tps features are active 8.200
When I write some files expected to persist 1.181
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.291
And all persistent directories from the old Tails version have safe access rights 1.773
And I take note of which tps features are available 6.435
And I shutdown Tails and wait for the computer to power off 2.519
# 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.611
After features/support/hooks.rb:339 0.550
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.694
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 without a persistent partition and stopped at Tails Greeter's login screen 8.456
And I log in to a new session 13.412
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.942
And I plug USB drive "to_upgrade" 2.238
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.540
Then the running Tails is installed on USB drive "to_upgrade" 16.866
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.116
After features/support/hooks.rb:339 0.793
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.204
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.629
Then all tps features from the old Tails version are active 1.380
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 2.619
And the expected persistent files created with the old Tails version are present in the filesystem 1.260
And all persistent directories from the old Tails version have safe access rights 1.837
After features/support/hooks.rb:339 0.957
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
3:39.263
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.383
And no SquashFS delta is installed 0.122
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
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.372
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.461
When the network is plugged 0.032
And Tor is ready 13.313
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.057
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.355
Given I shutdown Tails and wait for the computer to power off 6.889
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.994
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 7.743
And the file system changes introduced in version 6.2~testoverlayfs are present 0.347
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.183
# 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.229
When the network is plugged 0.026
And Tor is ready 10.440
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.869
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.698
Given I shutdown Tails and wait for the computer to power off 4.210
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.996
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 8.238
And the file system changes introduced in version 6.3~testoverlayfs are present 0.342
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.103
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.036
And Tor is ready 10.617
Then the Upgrader considers the system as up-to-date 0.188
# 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.140
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.316
After features/support/hooks.rb:339 0.633
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
19.296
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.904
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the signing key used by the Upgrader is outdated 0.086
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 8.638
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.270
After features/support/hooks.rb:339 0.827
After features/support/hooks.rb:108 0.000