Project Number Date
test_Tails_ISO_devel 4240 18 Feb 2026, 12:41

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 20:12.680 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:48.947
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.353
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 33.128
When I start Tails from USB drive "old" with network unplugged 1:9.048
Then the boot device has safe access rights 3.580
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.615
And I unplug USB drive "old" 0.654
After features/support/hooks.rb:331 2.064
After features/support/hooks.rb:100 0.012
Tags: @product
1:54.166
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:10.014
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 33.582
And I take note of which tps features are available 1.392
Then a Tails persistence partition exists on USB drive "old" 0.892
And I shutdown Tails and wait for the computer to power off 7.729
After features/support/hooks.rb:331 0.343
After features/support/hooks.rb:100 0.010
Tags: @product
2:1.213
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:25.143
Then Tails is running from USB drive "old" 0.918
And all tps features are active 2.369
When I write some files expected to persist 1.746
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.446
And all persistent directories from the old Tails version have safe access rights 2.445
And I take note of which tps features are available 0.448
And I shutdown Tails and wait for the computer to power off 7.802
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.452
After features/support/hooks.rb:331 0.268
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.606
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 13.362
And I log in to a new session 14.319
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.750
And I plug USB drive "to_upgrade" 2.403
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.289
Then the running Tails is installed on USB drive "to_upgrade" 27.806
And I unplug USB drive "to_upgrade" 1.019
And I unplug USB drive "__internal" 4.656
After features/support/hooks.rb:331 1.406
After features/support/hooks.rb:100 0.000
Tags: @product
1:44.297
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:34.402
Then all tps features from the old Tails version are active 2.501
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 3.051
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.450
After features/support/hooks.rb:331 16.300
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
9:22.308
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 1:4.614
And no SquashFS delta is installed 0.076
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.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.398
When the network is plugged 10.084
And Tor is ready 16.436
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.834
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 36.267
Given I shutdown Tails and wait for the computer to power off 12.761
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:24.305
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 18.441
And the file system changes introduced in version 6.2~testoverlayfs are present 0.356
And only the 6.2~testoverlayfs SquashFS delta is installed 0.151
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.621
# 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.688
When the network is plugged 0.070
And Tor is ready 32.256
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.603
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.740
Given I shutdown Tails and wait for the computer to power off 8.062
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:28.841
Then Tails is running version 6.3~testoverlayfs 0.093
And all tps features are active 6.097
And the file system changes introduced in version 6.3~testoverlayfs are present 0.525
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.203
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.243
When the network is plugged 0.575
And Tor is ready 42.411
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 6.089
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.687
After features/support/hooks.rb:331 1.084
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
29.141
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 12.032
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.118
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 12.201
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.417
After features/support/hooks.rb:331 1.030
After features/support/hooks.rb:100 0.000