Project Number Date
test_Tails_ISO_stable 6012 18 Dec 2025, 09:19

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 15:29.471 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:42.156
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.167
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 32.166
When I start Tails from USB drive "old" with network unplugged 1:4.859
Then the boot device has safe access rights 3.079
And Tails is running from USB drive "old" 0.260
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.074
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:331 3.857
After features/support/hooks.rb:100 0.011
Tags: @product
1:52.475
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:9.757
Then Tails is running from USB drive "old" 0.692
And I create a persistent partition 31.022
And I take note of which tps features are available 1.765
Then a Tails persistence partition exists on USB drive "old" 1.115
And I shutdown Tails and wait for the computer to power off 7.934
After features/support/hooks.rb:331 0.524
After features/support/hooks.rb:100 0.010
Tags: @product
1:53.605
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:18.462
Then Tails is running from USB drive "old" 0.727
And all tps features are active 1.950
When I write some files expected to persist 1.574
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.330
And all persistent directories from the old Tails version have safe access rights 2.446
And I take note of which tps features are available 0.465
And I shutdown Tails and wait for the computer to power off 7.806
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.463
After features/support/hooks.rb:331 0.418
After features/support/hooks.rb:100 0.012
Tags: @product
2:56.325
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 14.066
And I log in to a new session 18.483
And I clone USB drive "old" to a new USB drive "to_upgrade" 12.971
And I plug USB drive "to_upgrade" 2.753
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.187
Then the running Tails is installed on USB drive "to_upgrade" 23.351
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.287
After features/support/hooks.rb:331 3.859
After features/support/hooks.rb:100 0.000
Tags: @product
1:30.473
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:21.239
Then all tps features from the old Tails version are active 1.966
And Tails is running from USB drive "to_upgrade" 0.295
And the boot device has safe access rights 3.164
And the expected persistent files created with the old Tails version are present in the filesystem 1.360
And all persistent directories from the old Tails version have safe access rights 2.231
After features/support/hooks.rb:331 0.990
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:9.701
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 14.261
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.056
And Tor is ready 25.308
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.691
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.875
Given I shutdown Tails and wait for the computer to power off 11.942
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:24.269
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.714
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
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.165
# 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.292
When the network is plugged 0.077
And Tor is ready 12.239
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.981
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.522
Given I shutdown Tails and wait for the computer to power off 5.280
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.026
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.151
And the file system changes introduced in version 6.3~testoverlayfs are present 0.421
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.198
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.323
When the network is plugged 0.063
And Tor is ready 41.974
Then the Upgrader considers the system as up-to-date 0.122
# 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.543
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.604
After features/support/hooks.rb:331 1.404
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
24.734
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.005
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 11.514
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.725
After features/support/hooks.rb:331 1.169
After features/support/hooks.rb:100 0.000