Project Number Date
test_Tails_ISO_stable 6683 19 Sep 2026, 11:41

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:5.176 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:10.060
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.044
When I start Tails from USB drive "old" with network unplugged 53.527
Then the boot device has safe access rights 1.810
And Tails is running from USB drive "old" 0.190
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.027
And udev-watchdog is monitoring the correct device 0.174
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 1.751
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.953
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login 45.808
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 22.345
And I take note of which tps features are available 5.885
Then a Tails persistence partition exists on USB drive "old" 0.500
And I shutdown Tails and wait for the computer to power off 5.042
After features/support/hooks.rb:339 0.331
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.128
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.848
Then Tails is running from USB drive "old" 0.247
And all tps features are active 6.750
When I write some files expected to persist 0.985
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.264
And all persistent directories from the old Tails version have safe access rights 1.415
And I take note of which tps features are available 5.671
And I shutdown Tails and wait for the computer to power off 2.536
# 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.166
After features/support/hooks.rb:339 0.141
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.153
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.012
And I log in to a new session 10.800
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.557
And I plug USB drive "to_upgrade" 2.251
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.182
Then the running Tails is installed on USB drive "to_upgrade" 17.073
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 1.671
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.512
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.971
Then all tps features from the old Tails version are active 1.050
And Tails is running from USB drive "to_upgrade" 0.196
And the boot device has safe access rights 1.923
And the expected persistent files created with the old Tails version are present in the filesystem 0.804
And all persistent directories from the old Tails version have safe access rights 1.488
After features/support/hooks.rb:339 0.694
After features/support/hooks.rb:108 0.005
3:34.564
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.046
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.334
When the network is plugged 0.025
And Tor is ready 13.065
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.296
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 3.959
Given I shutdown Tails and wait for the computer to power off 5.249
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.762
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.556
And the file system changes introduced in version 6.2~testoverlayfs are present 0.233
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.090
# 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.178
When the network is plugged 0.036
And Tor is ready 16.262
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.286
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.083
Given I shutdown Tails and wait for the computer to power off 2.533
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.090
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.102
And the file system changes introduced in version 6.3~testoverlayfs are present 0.237
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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.151
When the network is plugged 0.037
And Tor is ready 10.067
Then the Upgrader considers the system as up-to-date 10.362
# 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.492
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.280
After features/support/hooks.rb:339 0.754
After features/support/hooks.rb:108 0.009
18.803
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 7.838
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.174
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
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.032
And Tor is ready 10.375
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.302
After features/support/hooks.rb:339 0.854
After features/support/hooks.rb:108 0.000