Project Number Date
test_Tails_ISO_devel 4409 22 May 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:36.754 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.911
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 13.876
When I start Tails from USB drive "old" with network unplugged 45.191
Then the boot device has safe access rights 3.019
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:335 3.724
After features/support/hooks.rb:104 0.005
Tags: @product
1:32.220
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 56.871
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 25.565
And I take note of which tps features are available 0.387
Then a Tails persistence partition exists on USB drive "old" 0.629
And I shutdown Tails and wait for the computer to power off 8.351
After features/support/hooks.rb:335 0.184
After features/support/hooks.rb:104 0.007
Tags: @product
1:29.859
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.898
Then Tails is running from USB drive "old" 0.271
And all tps features are active 1.129
When I write some files expected to persist 1.196
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.492
And all persistent directories from the old Tails version have safe access rights 2.294
And I take note of which tps features are available 0.175
And I shutdown Tails and wait for the computer to power off 8.029
# 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" 12.157
After features/support/hooks.rb:335 0.435
After features/support/hooks.rb:104 0.007
Tags: @product
2:11.475
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.262
And I log in to a new session 12.538
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.821
And I plug USB drive "to_upgrade" 2.243
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.963
Then the running Tails is installed on USB drive "to_upgrade" 15.355
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:335 1.941
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.796
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.199
Then all tps features from the old Tails version are active 1.120
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.770
And the expected persistent files created with the old Tails version are present in the filesystem 1.301
And all persistent directories from the old Tails version have safe access rights 2.116
After features/support/hooks.rb:335 0.956
After features/support/hooks.rb:104 0.015
3:46.338
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.505
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
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.198
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.349
When the network is plugged 0.015
And Tor is ready 12.399
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.065
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.744
Given I shutdown Tails and wait for the computer to power off 9.639
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.692
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.281
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.212
When the network is plugged 0.021
And Tor is ready 10.502
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.882
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.232
Given I shutdown Tails and wait for the computer to power off 8.171
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.743
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.347
And the file system changes introduced in version 6.3~testoverlayfs are present 0.346
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.213
When the network is plugged 0.018
And Tor is ready 11.276
Then the Upgrader considers the system as up-to-date 10.642
# 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.226
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.469
After features/support/hooks.rb:335 0.649
After features/support/hooks.rb:104 0.039
21.153
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.567
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.794
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.323
After features/support/hooks.rb:335 0.600
After features/support/hooks.rb:104 0.000