Project Number Date
test_Tails_ISO_stable 6208 16 Mar 2026, 15:33

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:37.093 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:27.916
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 15.563
When I start Tails from USB drive "old" with network unplugged 1:7.592
Then the boot device has safe access rights 2.993
And Tails is running from USB drive "old" 0.218
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.074
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:331 3.743
After features/support/hooks.rb:100 0.040
Tags: @product
1:31.932
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 55.518
Then Tails is running from USB drive "old" 0.279
And I create a persistent partition 26.224
And I take note of which tps features are available 0.834
Then a Tails persistence partition exists on USB drive "old" 0.639
And I shutdown Tails and wait for the computer to power off 8.344
After features/support/hooks.rb:331 0.507
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.507
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 "old" with network unplugged and I login with persistence enabled 1:4.479
Then Tails is running from USB drive "old" 0.304
And all tps features are active 1.484
When I write some files expected to persist 1.321
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.480
And all persistent directories from the old Tails version have safe access rights 2.256
And I take note of which tps features are available 0.159
And I shutdown Tails and wait for the computer to power off 8.251
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.450
After features/support/hooks.rb:331 0.352
After features/support/hooks.rb:100 0.008
Tags: @product
2:22.499
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.902
And I log in to a new session 15.427
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.785
And I plug USB drive "to_upgrade" 2.299
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.870
Then the running Tails is installed on USB drive "to_upgrade" 18.937
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 3.916
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.845
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.532
Then all tps features from the old Tails version are active 1.397
And Tails is running from USB drive "to_upgrade" 0.283
And the boot device has safe access rights 3.087
And the expected persistent files created with the old Tails version are present in the filesystem 1.376
And all persistent directories from the old Tails version have safe access rights 2.096
After features/support/hooks.rb:331 0.953
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:56.778
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 9.504
And no SquashFS delta is installed 0.149
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.350
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.516
When the network is plugged 0.028
And Tor is ready 23.687
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.431
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.430
Given I shutdown Tails and wait for the computer to power off 21.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.745
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.508
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.194
# 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.021
And Tor is ready 21.627
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.377
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.989
Given I shutdown Tails and wait for the computer to power off 18.374
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.498
Then Tails is running version 6.3~testoverlayfs 0.036
And all tps features are active 1.659
And the file system changes introduced in version 6.3~testoverlayfs are present 0.448
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.149
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.325
When the network is plugged 0.014
And Tor is ready 21.061
Then the Upgrader considers the system as up-to-date 0.143
# 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.916
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.539
After features/support/hooks.rb:331 1.037
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
28.613
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.631
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.036
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 20.236
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.372
After features/support/hooks.rb:331 0.781
After features/support/hooks.rb:100 0.000