Project Number Date
test_Tails_ISO_devel 4243 20 Feb 2026, 12:20

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 17:34.233 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:34.638
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 28.368
When I start Tails from USB drive "old" with network unplugged 1:1.106
Then the boot device has safe access rights 3.066
And Tails is running from USB drive "old" 0.292
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.249
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:331 1.397
After features/support/hooks.rb:100 0.010
Tags: @product
1:59.128
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:2.440
Then Tails is running from USB drive "old" 0.278
And I create a persistent partition 40.183
And I take note of which tps features are available 7.570
Then a Tails persistence partition exists on USB drive "old" 0.736
And I shutdown Tails and wait for the computer to power off 7.742
After features/support/hooks.rb:331 0.352
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.743
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:21.772
Then Tails is running from USB drive "old" 0.668
And all tps features are active 3.600
When I write some files expected to persist 1.507
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.324
And all persistent directories from the old Tails version have safe access rights 2.401
And I take note of which tps features are available 0.759
And I shutdown Tails and wait for the computer to power off 13.035
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.326
After features/support/hooks.rb:331 0.319
After features/support/hooks.rb:100 0.010
Tags: @product
3:24.411
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 without a persistent partition and stopped at Tails Greeter's login screen 25.189
And I log in to a new session 20.734
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.442
And I plug USB drive "to_upgrade" 7.168
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:5.972
Then the running Tails is installed on USB drive "to_upgrade" 22.181
And I unplug USB drive "to_upgrade" 0.490
And I unplug USB drive "__internal" 1.233
After features/support/hooks.rb:331 2.858
After features/support/hooks.rb:100 0.000
Tags: @product
2:0.592
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 13.273
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:37.896
Then all tps features from the old Tails version are active 1.465
And Tails is running from USB drive "to_upgrade" 0.282
And the boot device has safe access rights 3.850
And the expected persistent files created with the old Tails version are present in the filesystem 1.428
And all persistent directories from the old Tails version have safe access rights 2.396
After features/support/hooks.rb:331 0.882
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:0.884
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.489
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.047
And Tor is ready 42.556
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.653
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.080
Given I shutdown Tails and wait for the computer to power off 14.301
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:30.629
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 8.783
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
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.174
# 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.230
When the network is plugged 0.180
And Tor is ready 22.121
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.764
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.870
Given I shutdown Tails and wait for the computer to power off 18.592
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.565
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.527
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.182
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.249
When the network is plugged 0.059
And Tor is ready 23.023
Then the Upgrader considers the system as up-to-date 0.177
# 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 6.059
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.552
After features/support/hooks.rb:331 0.927
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
25.834
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.245
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 15.581
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.595
After features/support/hooks.rb:331 1.346
After features/support/hooks.rb:100 0.000