Project Number Date
test_Tails_ISO_stable 6284 09 Apr 2026, 14:22

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 13:44.582 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:14.183
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 15.592
When I start Tails from USB drive "old" with network unplugged 53.595
Then the boot device has safe access rights 3.135
And Tails is running from USB drive "old" 0.288
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 3.425
After features/support/hooks.rb:100 0.007
Tags: @product
1:36.581
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 1:1.430
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 25.097
And I take note of which tps features are available 0.904
Then a Tails persistence partition exists on USB drive "old" 0.578
And I shutdown Tails and wait for the computer to power off 8.227
After features/support/hooks.rb:331 0.312
After features/support/hooks.rb:100 0.008
Tags: @product
1:37.303
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.122
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.239
Then Tails is running from USB drive "old" 0.274
And all tps features are active 1.416
When I write some files expected to persist 1.296
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.454
And all persistent directories from the old Tails version have safe access rights 2.202
And I take note of which tps features are available 0.252
And I shutdown Tails and wait for the computer to power off 8.705
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.146
After features/support/hooks.rb:331 0.617
After features/support/hooks.rb:100 0.015
Tags: @product
2:22.163
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 8.616
And I log in to a new session 17.218
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.024
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.455
Then the running Tails is installed on USB drive "to_upgrade" 19.136
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.281
After features/support/hooks.rb:331 2.914
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.105
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.096
Then all tps features from the old Tails version are active 0.962
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.895
And the expected persistent files created with the old Tails version are present in the filesystem 1.260
And all persistent directories from the old Tails version have safe access rights 2.555
After features/support/hooks.rb:331 0.659
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
5:6.285
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 9.969
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.444
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.391
When the network is plugged 0.026
And Tor is ready 31.686
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.403
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.559
Given I shutdown Tails and wait for the computer to power off 21.684
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.140
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.140
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.175
When the network is plugged 0.017
And Tor is ready 23.230
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.436
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.383
Given I shutdown Tails and wait for the computer to power off 17.813
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.589
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.288
And the file system changes introduced in version 6.3~testoverlayfs are present 0.526
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.182
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.241
When the network is plugged 0.022
And Tor is ready 21.431
Then the Upgrader considers the system as up-to-date 0.132
# 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.033
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.376
After features/support/hooks.rb:331 0.923
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
29.958
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 7.988
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
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.060
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 21.215
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.374
After features/support/hooks.rb:331 0.831
After features/support/hooks.rb:100 0.000