Project Number Date
test_Tails_ISO_devel 4247 23 Feb 2026, 16:44

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 16:1.537 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:39.236
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.438
And I create a 7200 MiB disk named "old" 0.087
And I plug USB drive "old" 1.140
And I write an old version of the Tails USB image to disk "old" 33.750
When I start Tails from USB drive "old" with network unplugged 59.197
Then the boot device has safe access rights 3.604
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.276
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:331 1.467
After features/support/hooks.rb:100 0.012
Tags: @product
1:50.756
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:8.323
Then Tails is running from USB drive "old" 0.704
And I create a persistent partition 30.559
And I take note of which tps features are available 1.980
Then a Tails persistence partition exists on USB drive "old" 0.826
And I shutdown Tails and wait for the computer to power off 8.158
After features/support/hooks.rb:331 0.276
After features/support/hooks.rb:100 0.009
Tags: @product
1:51.291
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:17.439
Then Tails is running from USB drive "old" 0.633
And all tps features are active 2.010
When I write some files expected to persist 1.598
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 2.225
And I take note of which tps features are available 0.479
And I shutdown Tails and wait for the computer to power off 7.823
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.245
After features/support/hooks.rb:331 0.590
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.854
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 12.093
And I log in to a new session 12.595
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.421
And I plug USB drive "to_upgrade" 2.799
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.260
Then the running Tails is installed on USB drive "to_upgrade" 20.263
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:331 2.185
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.403
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.316
Then all tps features from the old Tails version are active 1.737
And Tails is running from USB drive "to_upgrade" 0.273
And the boot device has safe access rights 2.962
And the expected persistent files created with the old Tails version are present in the filesystem 1.426
And all persistent directories from the old Tails version have safe access rights 2.516
After features/support/hooks.rb:331 1.109
After features/support/hooks.rb:100 0.013
5:51.468
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.651
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
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.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.473
When the network is plugged 0.065
And Tor is ready 26.492
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.604
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.702
Given I shutdown Tails and wait for the computer to power off 23.362
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:29.914
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.337
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
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.177
# 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.052
And Tor is ready 42.498
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.629
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.491
Given I shutdown Tails and wait for the computer to power off 17.178
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:27.641
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.638
And the file system changes introduced in version 6.3~testoverlayfs are present 0.450
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.063
And Tor is ready 21.880
Then the Upgrader considers the system as up-to-date 0.134
# 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.729
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.534
After features/support/hooks.rb:331 1.230
After features/support/hooks.rb:100 0.018
53.525
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.188
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 41.231
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.642
After features/support/hooks.rb:331 0.974
After features/support/hooks.rb:100 0.000