Project Number Date
test_Tails_ISO_devel 4454 17 Jun 2026, 07:51

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:16.790 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
57.653
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.115
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 12.901
When I start Tails from USB drive "old" with network unplugged 40.265
Then the boot device has safe access rights 2.688
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.401
After features/support/hooks.rb:108 0.016
Tags: @product
1:21.780
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.106
And I start Tails from USB drive "old" with network unplugged and I login 50.850
Then Tails is running from USB drive "old" 0.273
And I create a persistent partition 23.383
And I take note of which tps features are available 3.895
Then a Tails persistence partition exists on USB drive "old" 0.517
And I shutdown Tails and wait for the computer to power off 2.753
After features/support/hooks.rb:339 0.544
After features/support/hooks.rb:108 0.017
Tags: @product
1:35.787
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.116
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.236
Then Tails is running from USB drive "old" 0.230
And all tps features are active 4.880
When I write some files expected to persist 1.326
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.141
And all persistence configuration files have safe access rights 0.328
And all persistent directories from the old Tails version have safe access rights 1.781
And I take note of which tps features are available 3.812
And I shutdown Tails and wait for the computer to power off 8.006
# 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.924
After features/support/hooks.rb:339 0.503
After features/support/hooks.rb:108 0.016
Tags: @product
2:7.986
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.902
And I log in to a new session 11.741
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.683
And I plug USB drive "to_upgrade" 2.189
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.911
Then the running Tails is installed on USB drive "to_upgrade" 14.300
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 2.198
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.059
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.108
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.592
Then all tps features from the old Tails version are active 1.013
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.324
And the expected persistent files created with the old Tails version are present in the filesystem 1.116
And all persistent directories from the old Tails version have safe access rights 1.668
After features/support/hooks.rb:339 0.624
After features/support/hooks.rb:108 0.016
3:43.950
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.331
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.014
And Tor is ready 11.649
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.377
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.126
Given I shutdown Tails and wait for the computer to power off 7.071
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.978
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.661
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.201
When the network is plugged 0.015
And Tor is ready 9.586
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.601
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.461
Given I shutdown Tails and wait for the computer to power off 8.157
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.415
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.867
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.118
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.014
And Tor is ready 9.577
Then the Upgrader considers the system as up-to-date 10.500
# 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.859
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.330
After features/support/hooks.rb:339 0.952
After features/support/hooks.rb:108 0.030
19.572
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.432
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.159
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.670
After features/support/hooks.rb:339 0.615
After features/support/hooks.rb:108 0.000