Project Number Date
test_Tails_ISO_update-onioncircuits-l10n-branch 1 15 Sep 2026, 15:05

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:20.319 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:27.084
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.157
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.106
When I start Tails from USB drive "old" with network unplugged 1:8.509
Then the boot device has safe access rights 2.638
And Tails is running from USB drive "old" 0.264
And there is no persistence partition on USB drive "old" 0.030
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.149
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.530
After features/support/hooks.rb:108 0.059
Tags: @product
1:28.978
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 51.542
Then Tails is running from USB drive "old" 0.215
And I create a persistent partition 25.155
And I take note of which tps features are available 7.253
Then a Tails persistence partition exists on USB drive "old" 0.601
And I shutdown Tails and wait for the computer to power off 4.127
After features/support/hooks.rb:339 0.423
After features/support/hooks.rb:108 0.006
Tags: @product
1:41.251
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.145
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.968
Then Tails is running from USB drive "old" 0.197
And all tps features are active 8.041
When I write some files expected to persist 1.065
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.272
And all persistent directories from the old Tails version have safe access rights 1.982
And I take note of which tps features are available 7.821
And I shutdown Tails and wait for the computer to power off 4.180
# 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.389
After features/support/hooks.rb:339 0.583
After features/support/hooks.rb:108 0.006
Tags: @product
2:17.238
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 without a persistent partition and stopped at Tails Greeter's login screen 9.588
And I log in to a new session 14.091
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.657
And I plug USB drive "to_upgrade" 2.325
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.300
Then the running Tails is installed on USB drive "to_upgrade" 19.013
And I unplug USB drive "to_upgrade" 0.152
And I unplug USB drive "__internal" 0.110
After features/support/hooks.rb:339 0.599
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.536
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.628
Then all tps features from the old Tails version are active 1.223
And Tails is running from USB drive "to_upgrade" 0.219
And the boot device has safe access rights 2.592
And the expected persistent files created with the old Tails version are present in the filesystem 1.018
And all persistent directories from the old Tails version have safe access rights 1.776
After features/support/hooks.rb:339 0.767
After features/support/hooks.rb:108 0.006
3:51.824
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.842
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.354
When the network is plugged 0.033
And Tor is ready 11.843
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.510
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.560
Given I shutdown Tails and wait for the computer to power off 5.749
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.715
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 11.682
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.092
# 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.189
When the network is plugged 0.029
And Tor is ready 10.685
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.767
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.334
Given I shutdown Tails and wait for the computer to power off 4.222
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.554
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.776
And the file system changes introduced in version 6.3~testoverlayfs are present 0.465
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.102
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.241
When the network is plugged 0.036
And Tor is ready 10.918
Then the Upgrader considers the system as up-to-date 0.109
# 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.558
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.386
After features/support/hooks.rb:339 0.622
After features/support/hooks.rb:108 0.013
20.405
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.122
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 9.607
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.339
After features/support/hooks.rb:339 0.909
After features/support/hooks.rb:108 0.000