Project Number Date
test_Tails_ISO_stable 5942 11 Nov 2025, 08:39

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:21.485 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.202
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 33.185
When I start Tails from USB drive "old" with network unplugged 1:30.084
Then the boot device has safe access rights 3.566
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.273
And I unplug USB drive "old" 0.336
After features/support/hooks.rb:331 3.727
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.503
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:26.069
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 30.001
And I take note of which tps features are available 1.275
Then a Tails persistence partition exists on USB drive "old" 0.759
And I shutdown Tails and wait for the computer to power off 7.894
After features/support/hooks.rb:331 0.525
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.348
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:39.619
Then Tails is running from USB drive "old" 0.441
And all tps features are active 2.091
When I write some files expected to persist 2.029
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.458
And all persistent directories from the old Tails version have safe access rights 2.417
And I take note of which tps features are available 0.503
And I shutdown Tails and wait for the computer to power off 7.734
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.629
After features/support/hooks.rb:331 0.623
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.919
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 12.731
And I log in to a new session 16.478
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.676
And I plug USB drive "to_upgrade" 2.367
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.600
Then the running Tails is installed on USB drive "to_upgrade" 22.620
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:331 4.106
After features/support/hooks.rb:100 0.000
Tags: @product
1:57.172
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:37.961
Then all tps features from the old Tails version are active 11.760
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.158
And the expected persistent files created with the old Tails version are present in the filesystem 1.386
And all persistent directories from the old Tails version have safe access rights 2.376
After features/support/hooks.rb:331 0.790
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:48.612
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 12.614
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.325
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.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.510
When the network is plugged 0.079
And Tor is ready 13.836
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.921
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.631
Given I shutdown Tails and wait for the computer to power off 11.431
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.122
Then Tails is running version 6.2~testoverlayfs 0.574
And all tps features are active 13.179
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.166
# 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.220
When the network is plugged 0.057
And Tor is ready 12.032
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.816
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.188
Given I shutdown Tails and wait for the computer to power off 10.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.509
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.201
And the file system changes introduced in version 6.3~testoverlayfs are present 0.545
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.239
When the network is plugged 0.067
And Tor is ready 13.396
Then the Upgrader considers the system as up-to-date 0.203
# 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 9.889
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.468
After features/support/hooks.rb:331 0.830
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
25.724
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.755
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
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.096
But a current signing key is available on our website 0.000
When the network is plugged 1.042
And Tor is ready 10.690
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.801
After features/support/hooks.rb:331 0.664
After features/support/hooks.rb:100 0.000