Project Number Date
test_Tails_ISO_update-onioncircuits-l10n-branch 2 15 Sep 2026, 15:23

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:39.793 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:4.449
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.135
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.914
When I start Tails from USB drive "old" with network unplugged 46.371
Then the boot device has safe access rights 2.361
And Tails is running from USB drive "old" 0.229
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 3.663
After features/support/hooks.rb:108 0.013
Tags: @product
1:24.317
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 49.918
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 22.983
And I take note of which tps features are available 6.378
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 4.205
After features/support/hooks.rb:339 0.553
After features/support/hooks.rb:108 0.007
Tags: @product
1:34.286
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.633
Then Tails is running from USB drive "old" 0.238
And all tps features are active 7.951
When I write some files expected to persist 0.945
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
And all persistence configuration files have safe access rights 0.239
And all persistent directories from the old Tails version have safe access rights 1.459
And I take note of which tps features are available 6.356
And I shutdown Tails and wait for the computer to power off 2.700
# 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.503
After features/support/hooks.rb:339 0.533
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.971
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 8.992
And I log in to a new session 11.213
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.689
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.958
Then the running Tails is installed on USB drive "to_upgrade" 19.670
And I unplug USB drive "to_upgrade" 0.110
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 1.687
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.717
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.211
Then all tps features from the old Tails version are active 1.071
And Tails is running from USB drive "to_upgrade" 0.208
And the boot device has safe access rights 2.286
And the expected persistent files created with the old Tails version are present in the filesystem 1.126
And all persistent directories from the old Tails version have safe access rights 1.733
After features/support/hooks.rb:339 0.521
After features/support/hooks.rb:108 0.027
3:49.212
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.178
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.198
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.297
When the network is plugged 0.033
And Tor is ready 11.781
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.741
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.074
Given I shutdown Tails and wait for the computer to power off 5.357
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.544
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 9.099
And the file system changes introduced in version 6.2~testoverlayfs are present 0.266
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.128
# 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.201
When the network is plugged 0.024
And Tor is ready 10.770
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.048
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.095
Given I shutdown Tails and wait for the computer to power off 3.939
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.506
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.332
And the file system changes introduced in version 6.3~testoverlayfs are present 0.309
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.182
When the network is plugged 0.030
And Tor is ready 10.114
Then the Upgrader considers the system as up-to-date 10.420
# 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.556
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.415
After features/support/hooks.rb:339 0.659
After features/support/hooks.rb:108 0.011
20.838
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.209
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 10.577
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.652
After features/support/hooks.rb:339 0.899
After features/support/hooks.rb:108 0.000