Project Number Date
test_Tails_ISO_devel 4658 05 Oct 2026, 17:30

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.140 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:13.693
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.484
When I start Tails from USB drive "old" with network unplugged 56.559
Then the boot device has safe access rights 1.940
And Tails is running from USB drive "old" 0.199
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.160
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:339 3.378
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.420
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 46.986
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 24.765
And I take note of which tps features are available 6.580
Then a Tails persistence partition exists on USB drive "old" 0.532
And I shutdown Tails and wait for the computer to power off 4.208
After features/support/hooks.rb:339 0.414
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.784
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.745
Then Tails is running from USB drive "old" 0.224
And all tps features are active 7.006
When I write some files expected to persist 1.476
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.348
And all persistent directories from the old Tails version have safe access rights 1.513
And I take note of which tps features are available 5.825
And I shutdown Tails and wait for the computer to power off 2.553
# 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.840
After features/support/hooks.rb:339 0.603
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.172
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.241
And I log in to a new session 12.544
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.735
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.489
Then the running Tails is installed on USB drive "to_upgrade" 18.618
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:339 1.736
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.537
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.049
Then all tps features from the old Tails version are active 1.194
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.477
And the expected persistent files created with the old Tails version are present in the filesystem 0.950
And all persistent directories from the old Tails version have safe access rights 1.550
After features/support/hooks.rb:339 0.647
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:28.726
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 8.056
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.320
When the network is plugged 0.027
And Tor is ready 11.939
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.033
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.624
Given I shutdown Tails and wait for the computer to power off 5.335
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.201
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.658
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.091
# 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.166
When the network is plugged 0.036
And Tor is ready 10.599
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.063
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.801
Given I shutdown Tails and wait for the computer to power off 2.638
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.331
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.638
And the file system changes introduced in version 6.3~testoverlayfs are present 0.320
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.032
And Tor is ready 10.063
Then the Upgrader considers the system as up-to-date 0.100
# 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.163
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.284
After features/support/hooks.rb:339 0.689
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
17.805
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.822
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
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.038
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 8.127
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.533
After features/support/hooks.rb:339 0.917
After features/support/hooks.rb:108 0.000