Project Number Date
test_Tails_ISO_devel 4360 23 Apr 2026, 11:04

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:50.316 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:4.796
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.061
And I create a 7200 MiB disk named "old" 0.016
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.144
When I start Tails from USB drive "old" with network unplugged 45.939
Then the boot device has safe access rights 2.816
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.218
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:331 3.801
After features/support/hooks.rb:100 0.007
Tags: @product
1:32.481
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 57.446
Then Tails is running from USB drive "old" 0.279
And I create a persistent partition 26.331
And I take note of which tps features are available 0.818
Then a Tails persistence partition exists on USB drive "old" 0.568
And I shutdown Tails and wait for the computer to power off 6.959
After features/support/hooks.rb:331 0.371
After features/support/hooks.rb:100 0.009
Tags: @product
1:34.154
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.391
Then Tails is running from USB drive "old" 0.267
And all tps features are active 1.094
When I write some files expected to persist 1.549
# 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.463
And all persistent directories from the old Tails version have safe access rights 2.137
And I take note of which tps features are available 0.349
And I shutdown Tails and wait for the computer to power off 8.477
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.174
After features/support/hooks.rb:331 0.318
After features/support/hooks.rb:100 0.014
Tags: @product
2:16.312
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.769
And I log in to a new session 14.065
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.926
And I plug USB drive "to_upgrade" 2.253
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.471
Then the running Tails is installed on USB drive "to_upgrade" 17.388
And I unplug USB drive "to_upgrade" 0.282
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:331 2.643
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.914
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.525
Then all tps features from the old Tails version are active 1.092
And Tails is running from USB drive "to_upgrade" 0.285
And the boot device has safe access rights 2.842
And the expected persistent files created with the old Tails version are present in the filesystem 1.234
And all persistent directories from the old Tails version have safe access rights 1.856
After features/support/hooks.rb:331 0.871
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:42.038
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.709
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.356
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.353
When the network is plugged 0.016
And Tor is ready 21.726
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.394
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.567
Given I shutdown Tails and wait for the computer to power off 20.397
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.154
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.212
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.190
# 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.236
When the network is plugged 0.015
And Tor is ready 21.452
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.486
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.735
Given I shutdown Tails and wait for the computer to power off 13.769
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.647
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.103
And the file system changes introduced in version 6.3~testoverlayfs are present 0.340
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.213
When the network is plugged 0.016
And Tor is ready 21.449
Then the Upgrader considers the system as up-to-date 0.100
# 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.069
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.470
After features/support/hooks.rb:331 1.009
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
26.618
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 7.924
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 17.970
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.370
After features/support/hooks.rb:331 0.635
After features/support/hooks.rb:100 0.000