Project Number Date
test_Tails_ISO_update-onioncircuits-l10n-branch 3 15 Sep 2026, 16: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 13:53.070 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:9.351
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 13.943
When I start Tails from USB drive "old" with network unplugged 51.686
Then the boot device has safe access rights 1.966
And Tails is running from USB drive "old" 0.213
And there is no persistence partition on USB drive "old" 0.032
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.710
After features/support/hooks.rb:108 0.029
Tags: @product
1:27.302
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 "old" with network unplugged and I login 50.538
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 24.253
And I take note of which tps features are available 6.992
Then a Tails persistence partition exists on USB drive "old" 0.647
And I shutdown Tails and wait for the computer to power off 4.490
After features/support/hooks.rb:339 0.552
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.446
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.123
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.499
Then Tails is running from USB drive "old" 0.200
And all tps features are active 7.647
When I write some files expected to persist 1.412
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 2.016
And I take note of which tps features are available 6.574
And I shutdown Tails and wait for the computer to power off 4.189
# 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.184
After features/support/hooks.rb:339 0.388
After features/support/hooks.rb:108 0.011
Tags: @product
2:15.419
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 without a persistent partition and stopped at Tails Greeter's login screen 8.813
And I log in to a new session 13.665
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.701
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.929
Then the running Tails is installed on USB drive "to_upgrade" 18.824
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:339 2.413
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.154
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.414
Then all tps features from the old Tails version are active 1.123
And Tails is running from USB drive "to_upgrade" 0.155
And the boot device has safe access rights 2.373
And the expected persistent files created with the old Tails version are present in the filesystem 1.179
And all persistent directories from the old Tails version have safe access rights 1.833
After features/support/hooks.rb:339 0.556
After features/support/hooks.rb:108 0.006
5:46.814
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.996
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.282
When the network is plugged 0.035
And Tor is ready 16.285
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2:3.588
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.737
Given I shutdown Tails and wait for the computer to power off 5.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.800
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.274
And the file system changes introduced in version 6.2~testoverlayfs are present 0.143
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.088
# 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.168
When the network is plugged 0.026
And Tor is ready 10.877
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.588
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.728
Given I shutdown Tails and wait for the computer to power off 5.122
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.124
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.222
And the file system changes introduced in version 6.3~testoverlayfs are present 0.411
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.089
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.032
And Tor is ready 10.575
Then the Upgrader considers the system as up-to-date 0.133
# 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.727
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.354
After features/support/hooks.rb:339 0.661
After features/support/hooks.rb:108 0.012
20.580
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.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 9.836
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.370
After features/support/hooks.rb:339 0.546
After features/support/hooks.rb:108 0.000