Project Number Date
test_Tails_ISO_devel 4502 21 Jul 2026, 08:10

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 12:11.232 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:15.937
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.099
When I start Tails from USB drive "old" with network unplugged 57.295
Then the boot device has safe access rights 2.597
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.268
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:339 3.725
After features/support/hooks.rb:108 0.018
Tags: @product
1:33.079
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 54.237
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 25.502
And I take note of which tps features are available 4.345
Then a Tails persistence partition exists on USB drive "old" 0.605
And I shutdown Tails and wait for the computer to power off 8.081
After features/support/hooks.rb:339 0.320
After features/support/hooks.rb:108 0.006
Tags: @product
1:44.773
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.521
Then Tails is running from USB drive "old" 0.229
And all tps features are active 5.609
When I write some files expected to persist 1.579
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.349
And all persistent directories from the old Tails version have safe access rights 2.181
And I take note of which tps features are available 4.469
And I shutdown Tails and wait for the computer to power off 8.129
# 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.487
After features/support/hooks.rb:339 0.618
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.210
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.281
And I log in to a new session 13.492
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.784
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.440
Then the running Tails is installed on USB drive "to_upgrade" 15.704
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 0.881
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.196
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.992
Then all tps features from the old Tails version are active 1.108
And Tails is running from USB drive "to_upgrade" 0.257
And the boot device has safe access rights 2.685
And the expected persistent files created with the old Tails version are present in the filesystem 1.294
And all persistent directories from the old Tails version have safe access rights 1.802
After features/support/hooks.rb:339 0.609
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:50.379
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 7.837
And no SquashFS delta is installed 0.181
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.017
And Tor is ready 12.730
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.574
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.514
Given I shutdown Tails and wait for the computer to power off 5.557
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.357
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 5.473
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
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.172
# 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.236
When the network is plugged 0.022
And Tor is ready 10.022
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.220
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.681
Given I shutdown Tails and wait for the computer to power off 4.202
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.319
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.721
And the file system changes introduced in version 6.3~testoverlayfs are present 0.428
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.022
And Tor is ready 10.265
Then the Upgrader considers the system as up-to-date 10.616
# 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 5.045
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.422
After features/support/hooks.rb:339 1.189
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.655
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 7.656
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.683
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.946
After features/support/hooks.rb:339 0.633
After features/support/hooks.rb:108 0.000