Project Number Date
test_Tails_ISO_stable 5935 06 Nov 2025, 14:23

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:38.092 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:58.863
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.781
When I start Tails from USB drive "old" with network unplugged 1:23.060
Then the boot device has safe access rights 2.943
And Tails is running from USB drive "old" 0.280
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:331 4.266
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.495
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login 1:25.587
Then Tails is running from USB drive "old" 0.295
And I create a persistent partition 29.849
And I take note of which tps features are available 3.356
Then a Tails persistence partition exists on USB drive "old" 0.675
And I shutdown Tails and wait for the computer to power off 7.566
After features/support/hooks.rb:331 0.469
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.848
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:34.593
Then Tails is running from USB drive "old" 0.335
And all tps features are active 1.701
When I write some files expected to persist 1.545
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.359
And all persistent directories from the old Tails version have safe access rights 2.210
And I take note of which tps features are available 0.438
And I shutdown Tails and wait for the computer to power off 7.973
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.290
After features/support/hooks.rb:331 0.628
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.171
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.016
And I log in to a new session 16.877
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.185
And I plug USB drive "to_upgrade" 3.157
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.613
Then the running Tails is installed on USB drive "to_upgrade" 20.897
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:331 3.886
After features/support/hooks.rb:100 0.000
Tags: @product
1:44.586
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.161
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:36.068
Then all tps features from the old Tails version are active 1.474
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 2.928
And the expected persistent files created with the old Tails version are present in the filesystem 1.315
And all persistent directories from the old Tails version have safe access rights 2.326
After features/support/hooks.rb:331 0.762
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:32.788
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.946
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.237
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.401
When the network is plugged 0.058
And Tor is ready 43.834
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.648
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.127
Given I shutdown Tails and wait for the computer to power off 11.177
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.387
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.998
And the file system changes introduced in version 6.2~testoverlayfs are present 0.257
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.223
When the network is plugged 0.060
And Tor is ready 12.233
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.753
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.479
Given I shutdown Tails and wait for the computer to power off 7.698
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:33.446
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.284
And the file system changes introduced in version 6.3~testoverlayfs are present 0.487
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.233
When the network is plugged 0.057
And Tor is ready 11.210
Then the Upgrader considers the system as up-to-date 10.840
# 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.401
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.476
After features/support/hooks.rb:331 0.824
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
24.337
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.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 10.941
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.783
After features/support/hooks.rb:331 1.050
After features/support/hooks.rb:100 0.000