Project Number Date
test_Tails_ISO_stable 5993 09 Dec 2025, 08:13

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 16:24.506 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
2:11.665
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.162
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.885
When I start Tails from USB drive "old" with network unplugged 1:32.735
Then the boot device has safe access rights 3.766
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.352
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:331 4.061
After features/support/hooks.rb:100 0.009
Tags: @product
2:23.240
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:34.024
Then Tails is running from USB drive "old" 0.684
And I create a persistent partition 29.964
And I take note of which tps features are available 1.562
Then a Tails persistence partition exists on USB drive "old" 6.317
And I shutdown Tails and wait for the computer to power off 10.481
After features/support/hooks.rb:331 0.330
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.947
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:38.802
Then Tails is running from USB drive "old" 0.317
And all tps features are active 1.932
When I write some files expected to persist 1.625
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.358
And all persistent directories from the old Tails version have safe access rights 2.876
And I take note of which tps features are available 0.713
And I shutdown Tails and wait for the computer to power off 7.905
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.048
After features/support/hooks.rb:331 0.457
After features/support/hooks.rb:100 0.008
Tags: @product
3:0.819
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.950
And I log in to a new session 17.125
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.871
And I plug USB drive "to_upgrade" 2.836
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:59.773
Then the running Tails is installed on USB drive "to_upgrade" 23.781
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.286
After features/support/hooks.rb:331 3.819
After features/support/hooks.rb:100 0.000
Tags: @product
1:34.644
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:23.301
Then all tps features from the old Tails version are active 1.526
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 4.835
And the expected persistent files created with the old Tails version are present in the filesystem 1.526
And all persistent directories from the old Tails version have safe access rights 2.948
After features/support/hooks.rb:331 1.095
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:33.460
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.599
And no SquashFS delta is installed 0.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.479
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.367
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.568
When the network is plugged 0.095
And Tor is ready 16.058
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.648
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.929
Given I shutdown Tails and wait for the computer to power off 11.211
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.675
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.884
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.171
# 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.312
When the network is plugged 0.336
And Tor is ready 13.920
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.664
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.063
Given I shutdown Tails and wait for the computer to power off 7.626
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.396
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.797
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.188
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.254
When the network is plugged 0.339
And Tor is ready 11.230
Then the Upgrader considers the system as up-to-date 0.162
# 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 6.718
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.536
After features/support/hooks.rb:331 0.982
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
26.727
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.815
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 13.113
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.271
After features/support/hooks.rb:331 1.212
After features/support/hooks.rb:100 0.000