Project Number Date
test_Tails_ISO_devel 4250 24 Feb 2026, 12:45

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.146 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:40.761
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.704
When I start Tails from USB drive "old" with network unplugged 1:2.835
Then the boot device has safe access rights 4.026
And Tails is running from USB drive "old" 0.287
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.077
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:331 3.553
After features/support/hooks.rb:100 0.009
Tags: @product
1:51.667
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:6.840
Then Tails is running from USB drive "old" 0.404
And I create a persistent partition 34.563
And I take note of which tps features are available 1.203
Then a Tails persistence partition exists on USB drive "old" 0.761
And I shutdown Tails and wait for the computer to power off 7.687
After features/support/hooks.rb:331 0.335
After features/support/hooks.rb:100 0.010
Tags: @product
1:54.595
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:19.513
Then Tails is running from USB drive "old" 0.628
And all tps features are active 2.627
When I write some files expected to persist 1.580
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 3.444
And I take note of which tps features are available 0.538
And I shutdown Tails and wait for the computer to power off 7.508
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.947
After features/support/hooks.rb:331 0.345
After features/support/hooks.rb:100 0.009
Tags: @product
2:39.818
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.580
And I log in to a new session 14.232
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.667
And I plug USB drive "to_upgrade" 3.123
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.515
Then the running Tails is installed on USB drive "to_upgrade" 22.284
And I unplug USB drive "to_upgrade" 0.183
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:331 3.727
After features/support/hooks.rb:100 0.000
Tags: @product
1:26.491
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:17.020
Then all tps features from the old Tails version are active 1.769
And Tails is running from USB drive "to_upgrade" 0.497
And the boot device has safe access rights 3.321
And the expected persistent files created with the old Tails version are present in the filesystem 1.473
And all persistent directories from the old Tails version have safe access rights 2.243
After features/support/hooks.rb:331 0.945
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:55.328
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 with a persistent partition enabled and logged in 11.354
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.589
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.224
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.605
When the network is plugged 0.052
And Tor is ready 28.309
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.634
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.179
Given I shutdown Tails and wait for the computer to power off 21.757
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:31.659
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.323
And the file system changes introduced in version 6.2~testoverlayfs are present 0.260
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.197
# 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.218
When the network is plugged 0.069
And Tor is ready 41.583
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.610
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.346
Given I shutdown Tails and wait for the computer to power off 18.337
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:29.997
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.560
And the file system changes introduced in version 6.3~testoverlayfs are present 0.436
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.052
And Tor is ready 23.744
Then the Upgrader considers the system as up-to-date 0.122
# 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.896
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.512
After features/support/hooks.rb:331 1.016
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
32.482
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 10.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 21.382
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.567
After features/support/hooks.rb:331 1.332
After features/support/hooks.rb:100 0.000