Project Number Date
test_Tails_ISO_devel 4164 14 Jan 2026, 09:14

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:28.022 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:35.819
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 30.629
When I start Tails from USB drive "old" with network unplugged 59.972
Then the boot device has safe access rights 3.149
And Tails is running from USB drive "old" 0.276
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.217
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:331 4.016
After features/support/hooks.rb:100 0.009
Tags: @product
1:34.524
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:0.473
Then Tails is running from USB drive "old" 0.302
And I create a persistent partition 28.610
And I take note of which tps features are available 1.157
Then a Tails persistence partition exists on USB drive "old" 0.704
And I shutdown Tails and wait for the computer to power off 3.106
After features/support/hooks.rb:331 0.460
After features/support/hooks.rb:100 0.009
Tags: @product
1:41.305
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.031
Then Tails is running from USB drive "old" 0.326
And all tps features are active 1.890
When I write some files expected to persist 1.637
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.183
And I take note of which tps features are available 0.435
And I shutdown Tails and wait for the computer to power off 7.547
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.490
After features/support/hooks.rb:331 0.560
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.189
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 without a persistent partition and stopped at Tails Greeter's login screen 11.513
And I log in to a new session 12.658
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.279
And I plug USB drive "to_upgrade" 2.379
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:56.738
Then the running Tails is installed on USB drive "to_upgrade" 19.218
And I unplug USB drive "to_upgrade" 0.171
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:331 3.867
After features/support/hooks.rb:100 0.000
Tags: @product
1:22.757
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:14.374
Then all tps features from the old Tails version are active 1.374
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.040
And the expected persistent files created with the old Tails version are present in the filesystem 1.260
And all persistent directories from the old Tails version have safe access rights 2.219
After features/support/hooks.rb:331 0.740
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:6.563
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.696
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
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.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.403
When the network is plugged 0.053
And Tor is ready 14.387
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.717
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.642
Given I shutdown Tails and wait for the computer to power off 12.400
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.996
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.048
And the file system changes introduced in version 6.2~testoverlayfs are present 0.274
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.186
# 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.251
When the network is plugged 0.077
And Tor is ready 12.294
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.620
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.566
Given I shutdown Tails and wait for the computer to power off 7.565
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.450
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.445
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.241
When the network is plugged 0.108
And Tor is ready 11.773
Then the Upgrader considers the system as up-to-date 0.160
# 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.223
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.489
After features/support/hooks.rb:331 1.071
After features/support/hooks.rb:100 0.046
Tags: @product @automatic_upgrade
22.860
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 10.799
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 10.981
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.582
After features/support/hooks.rb:331 0.978
After features/support/hooks.rb:100 0.000