Project Number Date
test_Tails_ISO_devel 4135 23 Dec 2025, 11:35

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:39.432 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:20.633
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 27.013
When I start Tails from USB drive "old" with network unplugged 48.524
Then the boot device has safe access rights 3.005
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.208
And I unplug USB drive "old" 0.162
After features/support/hooks.rb:331 3.576
After features/support/hooks.rb:100 0.010
Tags: @product
1:37.542
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 58.931
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 28.894
And I take note of which tps features are available 1.181
Then a Tails persistence partition exists on USB drive "old" 0.621
And I shutdown Tails and wait for the computer to power off 7.450
After features/support/hooks.rb:331 0.373
After features/support/hooks.rb:100 0.010
Tags: @product
1:46.769
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:13.973
Then Tails is running from USB drive "old" 0.614
And all tps features are active 1.834
When I write some files expected to persist 1.622
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 2.377
And I take note of which tps features are available 0.587
And I shutdown Tails and wait for the computer to power off 7.538
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.408
After features/support/hooks.rb:331 0.165
After features/support/hooks.rb:100 0.010
Tags: @product
2:17.332
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 9.788
And I log in to a new session 10.018
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.527
And I plug USB drive "to_upgrade" 2.403
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.653
Then the running Tails is installed on USB drive "to_upgrade" 18.559
And I unplug USB drive "to_upgrade" 0.186
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:331 3.993
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.333
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.698
Then all tps features from the old Tails version are active 1.421
And Tails is running from USB drive "to_upgrade" 0.296
And the boot device has safe access rights 3.165
And the expected persistent files created with the old Tails version are present in the filesystem 1.707
And all persistent directories from the old Tails version have safe access rights 2.846
After features/support/hooks.rb:331 0.680
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
3:56.267
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.496
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.431
When the network is plugged 0.049
And Tor is ready 12.477
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.738
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.681
Given I shutdown Tails and wait for the computer to power off 7.467
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.001
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.945
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.164
# 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.221
When the network is plugged 0.048
And Tor is ready 13.065
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.556
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.239
Given I shutdown Tails and wait for the computer to power off 7.502
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.256
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.088
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.249
When the network is plugged 0.058
And Tor is ready 12.294
Then the Upgrader considers the system as up-to-date 0.146
# 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.738
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.727
After features/support/hooks.rb:331 0.925
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
20.554
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 10.513
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.591
After features/support/hooks.rb:331 0.872
After features/support/hooks.rb:100 0.000