Project Number Date
test_Tails_ISO_update-design-doc 3 19 Sep 2026, 06:34

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:5.750 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:0.818
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 12.824
When I start Tails from USB drive "old" with network unplugged 44.446
Then the boot device has safe access rights 1.923
And Tails is running from USB drive "old" 0.188
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.034
And udev-watchdog is monitoring the correct device 0.136
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 1.891
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.163
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 47.133
Then Tails is running from USB drive "old" 0.219
And I create a persistent partition 22.111
And I take note of which tps features are available 5.883
Then a Tails persistence partition exists on USB drive "old" 0.463
And I shutdown Tails and wait for the computer to power off 5.268
After features/support/hooks.rb:339 0.136
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.639
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.805
Then Tails is running from USB drive "old" 0.183
And all tps features are active 6.852
When I write some files expected to persist 0.958
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.136
And all persistence configuration files have safe access rights 0.240
And all persistent directories from the old Tails version have safe access rights 1.548
And I take note of which tps features are available 6.068
And I shutdown Tails and wait for the computer to power off 2.506
# 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.252
After features/support/hooks.rb:339 0.168
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.498
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.150
And I log in to a new session 11.465
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.604
And I plug USB drive "to_upgrade" 2.569
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.377
Then the running Tails is installed on USB drive "to_upgrade" 17.035
And I unplug USB drive "to_upgrade" 0.111
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:339 1.555
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.842
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.175
Then all tps features from the old Tails version are active 0.921
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 2.031
And the expected persistent files created with the old Tails version are present in the filesystem 0.963
And all persistent directories from the old Tails version have safe access rights 1.462
After features/support/hooks.rb:339 0.784
After features/support/hooks.rb:108 0.042
3:41.794
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.006
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.284
When the network is plugged 0.024
And Tor is ready 11.374
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.898
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.552
Given I shutdown Tails and wait for the computer to power off 5.173
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.666
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.356
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.085
# 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.139
When the network is plugged 0.035
And Tor is ready 23.123
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.291
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.534
Given I shutdown Tails and wait for the computer to power off 2.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.890
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.153
And the file system changes introduced in version 6.3~testoverlayfs are present 0.231
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.096
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.056
And Tor is ready 10.329
Then the Upgrader considers the system as up-to-date 10.437
# 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.182
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.355
After features/support/hooks.rb:339 0.960
After features/support/hooks.rb:108 0.009
18.993
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.838
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
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.037
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 9.411
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.425
After features/support/hooks.rb:339 0.671
After features/support/hooks.rb:108 0.000