Project Number Date
test_Tails_ISO_stable 6042 07 Jan 2026, 11:27

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 12:21.735 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:19.349
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.197
When I start Tails from USB drive "old" with network unplugged 59.492
Then the boot device has safe access rights 3.740
And Tails is running from USB drive "old" 0.273
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.258
And I unplug USB drive "old" 0.158
After features/support/hooks.rb:331 4.049
After features/support/hooks.rb:100 0.009
Tags: @product
1:30.148
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login 55.515
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 24.737
And I take note of which tps features are available 0.734
Then a Tails persistence partition exists on USB drive "old" 0.613
And I shutdown Tails and wait for the computer to power off 8.079
After features/support/hooks.rb:331 0.307
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.916
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.105
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.040
Then Tails is running from USB drive "old" 0.258
And all tps features are active 1.407
When I write some files expected to persist 1.594
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.407
And all persistent directories from the old Tails version have safe access rights 2.220
And I take note of which tps features are available 0.236
And I shutdown Tails and wait for the computer to power off 8.311
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.102
After features/support/hooks.rb:331 0.459
After features/support/hooks.rb:100 0.007
Tags: @product
2:16.422
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.697
And I log in to a new session 14.294
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.857
And I plug USB drive "to_upgrade" 2.264
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.657
Then the running Tails is installed on USB drive "to_upgrade" 17.369
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:331 3.972
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.178
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.420
Then all tps features from the old Tails version are active 0.888
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 2.919
And the expected persistent files created with the old Tails version are present in the filesystem 1.177
And all persistent directories from the old Tails version have safe access rights 2.396
After features/support/hooks.rb:331 0.652
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
4:11.197
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.854
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
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.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.357
When the network is plugged 0.016
And Tor is ready 41.676
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.380
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.161
Given I shutdown Tails and wait for the computer to power off 7.022
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.476
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.262
And the file system changes introduced in version 6.2~testoverlayfs are present 0.240
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.139
# 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.208
When the network is plugged 0.015
And Tor is ready 11.810
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.938
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.602
Given I shutdown Tails and wait for the computer to power off 8.146
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.453
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.564
And the file system changes introduced in version 6.3~testoverlayfs are present 0.458
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.016
And Tor is ready 10.981
Then the Upgrader considers the system as up-to-date 10.638
# 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 4.224
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.420
After features/support/hooks.rb:331 0.781
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
21.522
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 8.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.291
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.656
After features/support/hooks.rb:331 0.690
After features/support/hooks.rb:100 0.000