Project Number Date
test_Tails_ISO_closed-issues-design-doc 2 28 May 2026, 18:01

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:42.999 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:28.830
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.103
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.094
When I start Tails from USB drive "old" with network unplugged 1:9.825
Then the boot device has safe access rights 3.035
And Tails is running from USB drive "old" 0.266
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.226
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:335 1.644
After features/support/hooks.rb:104 0.008
Tags: @product
1:36.681
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 1:0.744
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 26.860
And I take note of which tps features are available 0.342
Then a Tails persistence partition exists on USB drive "old" 0.659
And I shutdown Tails and wait for the computer to power off 7.734
After features/support/hooks.rb:335 0.183
After features/support/hooks.rb:104 0.009
Tags: @product
1:35.419
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.055
Then Tails is running from USB drive "old" 0.270
And all tps features are active 1.237
When I write some files expected to persist 1.426
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.475
And all persistent directories from the old Tails version have safe access rights 2.250
And I take note of which tps features are available 0.232
And I shutdown Tails and wait for the computer to power off 7.003
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 13.170
After features/support/hooks.rb:335 0.416
After features/support/hooks.rb:104 0.012
Tags: @product
2:18.849
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 9.624
And I log in to a new session 15.154
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.060
And I plug USB drive "to_upgrade" 2.311
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.504
Then the running Tails is installed on USB drive "to_upgrade" 17.772
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:335 2.960
After features/support/hooks.rb:104 0.000
Tags: @product
1:17.903
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.094
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.191
Then all tps features from the old Tails version are active 1.167
And Tails is running from USB drive "to_upgrade" 0.276
And the boot device has safe access rights 2.963
And the expected persistent files created with the old Tails version are present in the filesystem 1.895
And all persistent directories from the old Tails version have safe access rights 2.313
After features/support/hooks.rb:335 1.050
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
4:4.030
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.261
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.348
When the network is plugged 0.014
And Tor is ready 14.947
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.014
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.432
Given I shutdown Tails and wait for the computer to power off 10.277
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.523
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 1.511
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.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.188
# 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.240
When the network is plugged 0.019
And Tor is ready 10.115
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.398
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.123
Given I shutdown Tails and wait for the computer to power off 8.803
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.473
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.260
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.229
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.370
When the network is plugged 0.051
And Tor is ready 11.787
Then the Upgrader considers the system as up-to-date 10.637
# 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.990
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.399
After features/support/hooks.rb:335 1.048
After features/support/hooks.rb:104 0.016
Tags: @product @automatic_upgrade
21.284
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.738
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.043
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.840
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.283
After features/support/hooks.rb:335 1.052
After features/support/hooks.rb:104 0.000