Project Number Date
test_Tails_ISO_stable 5933 05 Nov 2025, 14:31

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 17:28.422 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:9.637
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.335
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 35.857
When I start Tails from USB drive "old" with network unplugged 1:28.027
Then the boot device has safe access rights 3.311
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.350
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:331 3.839
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.714
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 1:31.151
Then Tails is running from USB drive "old" 0.824
And I create a persistent partition 31.852
And I take note of which tps features are available 1.273
Then a Tails persistence partition exists on USB drive "old" 0.716
And I shutdown Tails and wait for the computer to power off 5.732
After features/support/hooks.rb:331 0.406
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.797
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:40.680
Then Tails is running from USB drive "old" 0.698
And all tps features are active 2.049
When I write some files expected to persist 1.745
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.139
And I take note of which tps features are available 0.426
And I shutdown Tails and wait for the computer to power off 7.715
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.557
After features/support/hooks.rb:331 0.149
After features/support/hooks.rb:100 0.014
Tags: @product
2:45.062
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 without a persistent partition and stopped at Tails Greeter's login screen 13.981
And I log in to a new session 18.486
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.463
And I plug USB drive "to_upgrade" 2.759
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.759
Then the running Tails is installed on USB drive "to_upgrade" 22.179
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:331 3.907
After features/support/hooks.rb:100 0.000
Tags: @product
1:49.604
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:40.782
Then all tps features from the old Tails version are active 1.875
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 2.765
And the expected persistent files created with the old Tails version are present in the filesystem 1.280
And all persistent directories from the old Tails version have safe access rights 2.396
After features/support/hooks.rb:331 0.994
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:52.175
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 13.697
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
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.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.048
And Tor is ready 15.685
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.895
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.017
Given I shutdown Tails and wait for the computer to power off 11.395
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.680
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.101
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.237
# 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.270
When the network is plugged 0.060
And Tor is ready 41.584
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.626
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.619
Given I shutdown Tails and wait for the computer to power off 7.727
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.997
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 3.354
And the file system changes introduced in version 6.3~testoverlayfs are present 0.655
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.168
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.056
And Tor is ready 11.177
Then the Upgrader considers the system as up-to-date 10.882
# 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.910
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.453
After features/support/hooks.rb:331 1.138
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
25.431
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 11.596
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.118
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 11.467
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.820
After features/support/hooks.rb:331 0.917
After features/support/hooks.rb:100 0.000