Project Number Date
test_Tails_ISO_update-design-doc 1 17 Sep 2026, 19:12

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:20.748 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:10.816
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.318
When I start Tails from USB drive "old" with network unplugged 53.674
Then the boot device has safe access rights 1.967
And Tails is running from USB drive "old" 0.182
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 3.711
After features/support/hooks.rb:108 0.012
Tags: @product
1:24.707
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 49.189
Then Tails is running from USB drive "old" 0.202
And I create a persistent partition 23.944
And I take note of which tps features are available 6.580
Then a Tails persistence partition exists on USB drive "old" 0.521
And I shutdown Tails and wait for the computer to power off 4.178
After features/support/hooks.rb:339 0.158
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.379
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.118
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.682
Then Tails is running from USB drive "old" 0.320
And all tps features are active 6.819
When I write some files expected to persist 1.127
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.261
And all persistent directories from the old Tails version have safe access rights 1.700
And I take note of which tps features are available 6.279
And I shutdown Tails and wait for the computer to power off 2.547
# 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.348
After features/support/hooks.rb:339 0.442
After features/support/hooks.rb:108 0.015
Tags: @product
2:13.050
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.604
And I log in to a new session 12.512
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.782
And I plug USB drive "to_upgrade" 2.214
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.391
Then the running Tails is installed on USB drive "to_upgrade" 17.293
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.591
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.141
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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:2.006
Then all tps features from the old Tails version are active 0.954
And Tails is running from USB drive "to_upgrade" 0.175
And the boot device has safe access rights 1.992
And the expected persistent files created with the old Tails version are present in the filesystem 1.164
And all persistent directories from the old Tails version have safe access rights 1.772
After features/support/hooks.rb:339 0.631
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
3:32.911
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.354
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.330
When the network is plugged 0.033
And Tor is ready 11.465
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.349
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.787
Given I shutdown Tails and wait for the computer to power off 5.204
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.590
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.978
And the file system changes introduced in version 6.2~testoverlayfs are present 0.184
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.114
# 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.210
When the network is plugged 0.039
And Tor is ready 10.195
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.174
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.781
Given I shutdown Tails and wait for the computer to power off 4.119
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.006
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.415
And the file system changes introduced in version 6.3~testoverlayfs are present 0.326
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.106
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.161
When the network is plugged 0.038
And Tor is ready 10.589
Then the Upgrader considers the system as up-to-date 0.106
# 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.249
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.350
After features/support/hooks.rb:339 0.952
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.742
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 7.745
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 11.135
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.516
After features/support/hooks.rb:339 0.954
After features/support/hooks.rb:108 0.000