Project Number Date
test_Tails_ISO_stable 5920 30 Oct 2025, 17: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 16:18.182 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:8.648
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.235
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 31.581
When I start Tails from USB drive "old" with network unplugged 1:32.073
Then the boot device has safe access rights 2.827
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.228
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:331 3.741
After features/support/hooks.rb:100 0.010
Tags: @product
2:7.506
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:26.366
Then Tails is running from USB drive "old" 0.791
And I create a persistent partition 29.709
And I take note of which tps features are available 1.336
Then a Tails persistence partition exists on USB drive "old" 0.755
And I shutdown Tails and wait for the computer to power off 8.355
After features/support/hooks.rb:331 0.596
After features/support/hooks.rb:100 0.014
Tags: @product
2:14.982
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:39.882
Then Tails is running from USB drive "old" 0.747
And all tps features are active 2.084
When I write some files expected to persist 1.848
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 2.431
And I take note of which tps features are available 0.496
And I shutdown Tails and wait for the computer to power off 7.914
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.726
After features/support/hooks.rb:331 0.476
After features/support/hooks.rb:100 0.010
Tags: @product
2:38.886
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 without a persistent partition and stopped at Tails Greeter's login screen 13.214
And I log in to a new session 17.006
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.346
And I plug USB drive "to_upgrade" 2.427
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.604
Then the running Tails is installed on USB drive "to_upgrade" 21.538
And I unplug USB drive "to_upgrade" 0.508
And I unplug USB drive "__internal" 0.240
After features/support/hooks.rb:331 4.273
After features/support/hooks.rb:100 0.000
Tags: @product
1:46.769
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:38.032
Then all tps features from the old Tails version are active 1.602
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 3.140
And the expected persistent files created with the old Tails version are present in the filesystem 1.367
And all persistent directories from the old Tails version have safe access rights 2.143
After features/support/hooks.rb:331 0.717
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:58.089
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 14.535
And no SquashFS delta is installed 0.194
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.060
And Tor is ready 14.248
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.923
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.458
Given I shutdown Tails and wait for the computer to power off 11.109
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.795
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.187
And the file system changes introduced in version 6.2~testoverlayfs are present 0.351
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.177
# 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.219
When the network is plugged 0.057
And Tor is ready 11.875
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.652
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.539
Given I shutdown Tails and wait for the computer to power off 4.768
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.374
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.375
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.068
# 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.265
When the network is plugged 0.059
And Tor is ready 13.817
Then the Upgrader considers the system as up-to-date 0.234
# 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.360
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.493
After features/support/hooks.rb:331 0.703
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
23.299
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.219
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 10.944
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.604
After features/support/hooks.rb:331 1.028
After features/support/hooks.rb:100 0.000