Project Number Date
test_Tails_ISO_stable 5936 07 Nov 2025, 12:08

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 15:57.908 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
2:25.304
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.161
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 43.752
When I start Tails from USB drive "old" with network unplugged 1:36.464
Then the boot device has safe access rights 2.958
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.265
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:331 3.540
After features/support/hooks.rb:100 0.012
Tags: @product
1:57.374
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 1:25.066
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 27.006
And I take note of which tps features are available 1.097
Then a Tails persistence partition exists on USB drive "old" 0.630
And I shutdown Tails and wait for the computer to power off 3.076
After features/support/hooks.rb:331 0.616
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.592
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.157
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:34.830
Then Tails is running from USB drive "old" 0.287
And all tps features are active 2.347
When I write some files expected to persist 1.604
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.346
And all persistent directories from the old Tails version have safe access rights 2.737
And I take note of which tps features are available 0.610
And I shutdown Tails and wait for the computer to power off 5.063
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.400
After features/support/hooks.rb:331 0.371
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.915
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 12.165
And I log in to a new session 15.907
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.818
And I plug USB drive "to_upgrade" 2.707
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.160
Then the running Tails is installed on USB drive "to_upgrade" 20.521
And I unplug USB drive "to_upgrade" 0.328
And I unplug USB drive "__internal" 0.306
After features/support/hooks.rb:331 4.198
After features/support/hooks.rb:100 0.000
Tags: @product
1:44.669
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.166
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:35.774
Then all tps features from the old Tails version are active 1.626
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 3.111
And the expected persistent files created with the old Tails version are present in the filesystem 1.354
And all persistent directories from the old Tails version have safe access rights 2.329
After features/support/hooks.rb:331 0.754
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:46.803
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 12.187
And no SquashFS delta is installed 0.140
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.315
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.536
When the network is plugged 0.084
And Tor is ready 14.902
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.983
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.711
Given I shutdown Tails and wait for the computer to power off 11.382
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.106
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.970
And the file system changes introduced in version 6.2~testoverlayfs are present 0.253
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.210
When the network is plugged 0.058
And Tor is ready 12.042
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.565
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.767
Given I shutdown Tails and wait for the computer to power off 5.020
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:34.889
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.026
And the file system changes introduced in version 6.3~testoverlayfs are present 0.453
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.218
When the network is plugged 0.060
And Tor is ready 11.007
Then the Upgrader considers the system as up-to-date 0.209
# 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.283
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.538
After features/support/hooks.rb:331 0.898
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
23.248
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 10.924
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.084
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.050
And Tor is ready 11.228
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.618
After features/support/hooks.rb:331 1.331
After features/support/hooks.rb:100 0.000