Project Number Date
test_Tails_ISO_closed-issues-design-doc 4 29 May 2026, 15:18

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 11:51.423 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:18.742
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.009
Given a computer 0.067
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.873
When I start Tails from USB drive "old" with network unplugged 1:0.391
Then the boot device has safe access rights 2.577
And Tails is running from USB drive "old" 0.227
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.156
After features/support/hooks.rb:335 1.549
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.658
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login 55.681
Then Tails is running from USB drive "old" 0.245
And I create a persistent partition 25.970
And I take note of which tps features are available 0.337
Then a Tails persistence partition exists on USB drive "old" 0.717
And I shutdown Tails and wait for the computer to power off 4.641
After features/support/hooks.rb:335 0.191
After features/support/hooks.rb:104 0.007
Tags: @product
1:28.686
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.648
Then Tails is running from USB drive "old" 0.283
And all tps features are active 1.119
When I write some files expected to persist 1.392
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.170
And all persistence configuration files have safe access rights 0.297
And all persistent directories from the old Tails version have safe access rights 1.875
And I take note of which tps features are available 0.145
And I shutdown Tails and wait for the computer to power off 8.532
# 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" 12.171
After features/support/hooks.rb:335 0.148
After features/support/hooks.rb:104 0.008
Tags: @product
2:14.086
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 8.703
And I log in to a new session 14.029
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.885
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.252
Then the running Tails is installed on USB drive "to_upgrade" 15.641
And I unplug USB drive "to_upgrade" 0.162
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:335 2.526
After features/support/hooks.rb:104 0.000
Tags: @product
1:8.779
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.652
Then all tps features from the old Tails version are active 1.012
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 2.480
And the expected persistent files created with the old Tails version are present in the filesystem 1.199
And all persistent directories from the old Tails version have safe access rights 2.058
After features/support/hooks.rb:335 0.954
After features/support/hooks.rb:104 0.029
Tags: @product @automatic_upgrade
3:52.342
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.037
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.698
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.356
When the network is plugged 0.017
And Tor is ready 12.833
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.594
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.204
Given I shutdown Tails and wait for the computer to power off 10.768
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.015
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.331
And the file system changes introduced in version 6.2~testoverlayfs are present 0.235
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.229
When the network is plugged 0.017
And Tor is ready 9.847
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.501
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.510
Given I shutdown Tails and wait for the computer to power off 8.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.871
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.146
And the file system changes introduced in version 6.3~testoverlayfs are present 0.437
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.493
When the network is plugged 0.025
And Tor is ready 16.791
Then the Upgrader considers the system as up-to-date 10.676
# 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.135
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.335
After features/support/hooks.rb:335 1.016
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
21.128
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.602
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 10.014
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.090
After features/support/hooks.rb:335 0.626
After features/support/hooks.rb:104 0.000