Project Number Date
test_Tails_ISO_stable 6193 10 Mar 2026, 14:46

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 12:53.896 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:13.725
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.648
When I start Tails from USB drive "old" with network unplugged 54.359
Then the boot device has safe access rights 2.887
And Tails is running from USB drive "old" 0.257
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:331 4.069
After features/support/hooks.rb:100 0.007
Tags: @product
1:34.011
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 59.159
Then Tails is running from USB drive "old" 0.286
And I create a persistent partition 25.933
And I take note of which tps features are available 0.826
Then a Tails persistence partition exists on USB drive "old" 0.643
And I shutdown Tails and wait for the computer to power off 7.094
After features/support/hooks.rb:331 0.377
After features/support/hooks.rb:100 0.011
Tags: @product
1:31.632
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.801
Then Tails is running from USB drive "old" 0.288
And all tps features are active 1.198
When I write some files expected to persist 1.472
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.665
And all persistent directories from the old Tails version have safe access rights 2.374
And I take note of which tps features are available 0.222
And I shutdown Tails and wait for the computer to power off 8.497
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.849
After features/support/hooks.rb:331 0.229
After features/support/hooks.rb:100 0.018
Tags: @product
2:17.033
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 9.030
And I log in to a new session 13.495
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.020
And I plug USB drive "to_upgrade" 2.286
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.645
Then the running Tails is installed on USB drive "to_upgrade" 17.217
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:331 2.321
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.541
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.907
Then all tps features from the old Tails version are active 0.958
And Tails is running from USB drive "to_upgrade" 0.221
And the boot device has safe access rights 2.804
And the expected persistent files created with the old Tails version are present in the filesystem 1.505
And all persistent directories from the old Tails version have safe access rights 2.076
After features/support/hooks.rb:331 0.691
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:35.408
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 9.526
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.315
When the network is plugged 0.022
And Tor is ready 21.295
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.377
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.780
Given I shutdown Tails and wait for the computer to power off 19.540
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.318
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.167
And the file system changes introduced in version 6.2~testoverlayfs are present 0.211
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.172
# 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.220
When the network is plugged 0.018
And Tor is ready 22.975
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.384
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.949
Given I shutdown Tails and wait for the computer to power off 13.652
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.280
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.326
And the file system changes introduced in version 6.3~testoverlayfs are present 0.489
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.015
And Tor is ready 21.920
Then the Upgrader considers the system as up-to-date 0.113
# 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 4.713
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.463
After features/support/hooks.rb:331 1.012
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
27.543
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
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.014
And Tor is ready 18.688
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.373
After features/support/hooks.rb:331 0.944
After features/support/hooks.rb:100 0.000