Project Number Date
test_Tails_ISO_stable 6125 06 Feb 2026, 11:52

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 14:19.085 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.442
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.107
And I write an old version of the Tails USB image to disk "old" 35.632
When I start Tails from USB drive "old" with network unplugged 58.153
Then the boot device has safe access rights 3.379
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:331 1.345
After features/support/hooks.rb:100 0.009
Tags: @product
1:45.067
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.155
And I start Tails from USB drive "old" with network unplugged and I login 1:5.659
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 29.358
And I take note of which tps features are available 1.191
Then a Tails persistence partition exists on USB drive "old" 0.749
And I shutdown Tails and wait for the computer to power off 7.646
After features/support/hooks.rb:331 0.382
After features/support/hooks.rb:100 0.010
Tags: @product
1:52.104
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:17.755
Then Tails is running from USB drive "old" 0.326
And all tps features are active 2.068
When I write some files expected to persist 1.542
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.375
And all persistent directories from the old Tails version have safe access rights 2.422
And I take note of which tps features are available 0.558
And I shutdown Tails and wait for the computer to power off 8.170
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.518
After features/support/hooks.rb:331 0.376
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.497
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 10.027
And I log in to a new session 10.121
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.322
And I plug USB drive "to_upgrade" 3.443
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.262
Then the running Tails is installed on USB drive "to_upgrade" 19.900
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:331 1.766
After features/support/hooks.rb:100 0.000
Tags: @product
1:28.432
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:18.716
Then all tps features from the old Tails version are active 1.387
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.258
And the expected persistent files created with the old Tails version are present in the filesystem 1.467
And all persistent directories from the old Tails version have safe access rights 3.057
After features/support/hooks.rb:331 1.038
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
4:45.444
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.856
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
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.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.062
And Tor is ready 12.910
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.841
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.851
Given I shutdown Tails and wait for the computer to power off 8.154
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.617
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.515
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.106
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.171
# 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.270
When the network is plugged 0.053
And Tor is ready 12.772
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.093
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.425
Given I shutdown Tails and wait for the computer to power off 7.769
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.389
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.670
And the file system changes introduced in version 6.3~testoverlayfs are present 0.774
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.232
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.059
And Tor is ready 41.275
Then the Upgrader considers the system as up-to-date 0.239
# 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.088
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.504
After features/support/hooks.rb:331 0.993
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
23.097
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.400
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.079
And the signing key used by the Upgrader is outdated 0.192
But a current signing key is available on our website 0.000
When the network is plugged 0.133
And Tor is ready 11.255
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.757
After features/support/hooks.rb:331 0.808
After features/support/hooks.rb:100 0.000