Project Number Date
test_Tails_ISO_devel 4463 21 Jun 2026, 11:36

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:36.737 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:9.241
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.126
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 13.258
When I start Tails from USB drive "old" with network unplugged 51.725
Then the boot device has safe access rights 2.375
And Tails is running from USB drive "old" 0.243
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 3.869
After features/support/hooks.rb:108 0.020
Tags: @product
1:29.873
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.159
And I start Tails from USB drive "old" with network unplugged and I login 51.774
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 24.476
And I take note of which tps features are available 4.188
Then a Tails persistence partition exists on USB drive "old" 0.543
And I shutdown Tails and wait for the computer to power off 8.401
After features/support/hooks.rb:339 0.441
After features/support/hooks.rb:108 0.021
Tags: @product
1:29.793
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.129
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.150
Then Tails is running from USB drive "old" 0.206
And all tps features are active 4.611
When I write some files expected to persist 1.223
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.258
And all persistent directories from the old Tails version have safe access rights 1.956
And I take note of which tps features are available 3.477
And I shutdown Tails and wait for the computer to power off 2.771
# 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.815
After features/support/hooks.rb:339 0.563
After features/support/hooks.rb:108 0.039
Tags: @product
2:9.829
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.012
And I log in to a new session 12.414
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.771
And I plug USB drive "to_upgrade" 2.186
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.149
Then the running Tails is installed on USB drive "to_upgrade" 15.027
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 3.809
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.403
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.158
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.721
Then all tps features from the old Tails version are active 1.023
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 2.504
And the expected persistent files created with the old Tails version are present in the filesystem 1.045
And all persistent directories from the old Tails version have safe access rights 1.737
After features/support/hooks.rb:339 0.852
After features/support/hooks.rb:108 0.021
3:47.714
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.415
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.237
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.305
When the network is plugged 0.016
And Tor is ready 13.351
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.936
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.493
Given I shutdown Tails and wait for the computer to power off 9.760
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.325
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.959
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.124
# 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.222
When the network is plugged 0.016
And Tor is ready 10.697
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.881
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.977
Given I shutdown Tails and wait for the computer to power off 7.070
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.746
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.356
And the file system changes introduced in version 6.3~testoverlayfs are present 0.323
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.167
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.223
When the network is plugged 0.014
And Tor is ready 9.478
Then the Upgrader considers the system as up-to-date 10.532
# 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.953
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.378
After features/support/hooks.rb:339 0.723
After features/support/hooks.rb:108 0.039
20.881
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.915
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
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.042
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.667
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.989
After features/support/hooks.rb:339 0.885
After features/support/hooks.rb:108 0.000