Project Number Date
test_Tails_ISO_devel 4309 01 Apr 2026, 11: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 13:9.033 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:5.646
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 15.054
When I start Tails from USB drive "old" with network unplugged 45.847
Then the boot device has safe access rights 2.954
And Tails is running from USB drive "old" 0.254
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:331 1.157
After features/support/hooks.rb:100 0.006
Tags: @product
1:36.731
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 "old" with network unplugged and I login 56.920
Then Tails is running from USB drive "old" 0.225
And I create a persistent partition 28.404
And I take note of which tps features are available 1.360
Then a Tails persistence partition exists on USB drive "old" 0.822
And I shutdown Tails and wait for the computer to power off 8.942
After features/support/hooks.rb:331 0.176
After features/support/hooks.rb:100 0.010
Tags: @product
1:32.869
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.112
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.894
Then Tails is running from USB drive "old" 0.508
And all tps features are active 1.405
When I write some files expected to persist 1.410
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.276
And all persistence configuration files have safe access rights 0.493
And all persistent directories from the old Tails version have safe access rights 2.334
And I take note of which tps features are available 0.224
And I shutdown Tails and wait for the computer to power off 4.214
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.995
After features/support/hooks.rb:331 0.536
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.504
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.835
And I log in to a new session 15.096
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.107
And I plug USB drive "to_upgrade" 2.247
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.722
Then the running Tails is installed on USB drive "to_upgrade" 16.185
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:331 2.081
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.799
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.380
Then all tps features from the old Tails version are active 1.032
And Tails is running from USB drive "to_upgrade" 0.280
And the boot device has safe access rights 2.993
And the expected persistent files created with the old Tails version are present in the filesystem 1.460
And all persistent directories from the old Tails version have safe access rights 2.574
After features/support/hooks.rb:331 1.025
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:50.682
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 9.221
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.294
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.378
When the network is plugged 0.028
And Tor is ready 23.076
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.446
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.420
Given I shutdown Tails and wait for the computer to power off 21.227
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.941
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.325
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.101
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.189
# 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.263
When the network is plugged 0.014
And Tor is ready 21.101
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.438
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.617
Given I shutdown Tails and wait for the computer to power off 8.431
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.479
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.384
And the file system changes introduced in version 6.3~testoverlayfs are present 0.437
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.162
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.340
When the network is plugged 0.024
And Tor is ready 21.208
Then the Upgrader considers the system as up-to-date 0.099
# 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.873
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.387
After features/support/hooks.rb:331 0.945
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
28.799
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 with a persistent partition enabled and logged in 8.266
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.043
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 19.599
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.531
After features/support/hooks.rb:331 1.316
After features/support/hooks.rb:100 0.000