Project Number Date
test_Tails_ISO_update-design-doc 2 18 Sep 2026, 06:24

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:34.024 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:5.346
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.240
When I start Tails from USB drive "old" with network unplugged 47.880
Then the boot device has safe access rights 2.489
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.178
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.718
After features/support/hooks.rb:108 0.037
Tags: @product
1:25.289
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 49.843
Then Tails is running from USB drive "old" 0.209
And I create a persistent partition 22.997
And I take note of which tps features are available 6.439
Then a Tails persistence partition exists on USB drive "old" 0.501
And I shutdown Tails and wait for the computer to power off 5.219
After features/support/hooks.rb:339 0.777
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.162
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.324
Then Tails is running from USB drive "old" 0.222
And all tps features are active 7.420
When I write some files expected to persist 1.376
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.293
And all persistent directories from the old Tails version have safe access rights 1.771
And I take note of which tps features are available 5.886
And I shutdown Tails and wait for the computer to power off 3.868
# 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" 11.623
After features/support/hooks.rb:339 0.145
After features/support/hooks.rb:108 0.005
Tags: @product
2:16.461
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.890
And I log in to a new session 12.054
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.118
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.050
Then the running Tails is installed on USB drive "to_upgrade" 19.843
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 2.086
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.748
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.088
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.085
Then all tps features from the old Tails version are active 1.138
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 2.129
And the expected persistent files created with the old Tails version are present in the filesystem 1.146
And all persistent directories from the old Tails version have safe access rights 1.955
After features/support/hooks.rb:339 0.941
After features/support/hooks.rb:108 0.024
Tags: @product @automatic_upgrade
3:34.280
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.411
And no SquashFS delta is installed 0.078
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.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.241
When the network is plugged 0.037
And Tor is ready 12.158
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.036
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.060
Given I shutdown Tails and wait for the computer to power off 5.281
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.491
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.370
And the file system changes introduced in version 6.2~testoverlayfs are present 0.168
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.150
When the network is plugged 0.038
And Tor is ready 10.381
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.009
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.599
Given I shutdown Tails and wait for the computer to power off 2.622
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.489
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.391
And the file system changes introduced in version 6.3~testoverlayfs are present 0.354
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.178
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.214
When the network is plugged 0.037
And Tor is ready 10.558
Then the Upgrader considers the system as up-to-date 0.086
# 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 3.659
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.390
After features/support/hooks.rb:339 0.670
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
28.735
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.281
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.031
And the signing key used by the Upgrader is outdated 0.030
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 19.799
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.321
After features/support/hooks.rb:339 0.955
After features/support/hooks.rb:108 0.000