Project Number Date
test_Tails_ISO_devel 4551 16 Aug 2026, 11:10

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 10:58.632 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:7.966
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
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.208
When I start Tails from USB drive "old" with network unplugged 51.214
Then the boot device has safe access rights 1.901
And Tails is running from USB drive "old" 0.155
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.032
And udev-watchdog is monitoring the correct device 0.168
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.631
After features/support/hooks.rb:108 0.067
Tags: @product
1:17.948
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login 46.241
Then Tails is running from USB drive "old" 0.159
And I create a persistent partition 22.411
And I take note of which tps features are available 6.009
Then a Tails persistence partition exists on USB drive "old" 0.464
And I shutdown Tails and wait for the computer to power off 2.555
After features/support/hooks.rb:339 0.349
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.553
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 with persistence enabled 59.616
Then Tails is running from USB drive "old" 0.222
And all tps features are active 7.143
When I write some files expected to persist 0.946
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.297
And all persistent directories from the old Tails version have safe access rights 1.463
And I take note of which tps features are available 5.964
And I shutdown Tails and wait for the computer to power off 2.497
# 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.145
After features/support/hooks.rb:339 0.273
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.522
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.307
And I log in to a new session 11.065
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.579
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.574
Then the running Tails is installed on USB drive "to_upgrade" 17.527
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.107
After features/support/hooks.rb:339 1.597
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.804
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.126
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.612
Then all tps features from the old Tails version are active 1.229
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.150
And the expected persistent files created with the old Tails version are present in the filesystem 0.903
And all persistent directories from the old Tails version have safe access rights 1.542
After features/support/hooks.rb:339 0.812
After features/support/hooks.rb:108 0.006
3:27.848
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.080
And no SquashFS delta is installed 0.053
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.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.287
When the network is plugged 0.032
And Tor is ready 11.664
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.391
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.747
Given I shutdown Tails and wait for the computer to power off 5.283
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.425
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.242
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# 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.188
When the network is plugged 0.026
And Tor is ready 10.263
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.468
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.717
Given I shutdown Tails and wait for the computer to power off 2.560
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.035
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 7.040
And the file system changes introduced in version 6.3~testoverlayfs are present 0.262
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.212
When the network is plugged 0.025
And Tor is ready 13.479
Then the Upgrader considers the system as up-to-date 0.075
# 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 2.935
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.319
After features/support/hooks.rb:339 0.991
After features/support/hooks.rb:108 0.024
18.990
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 8.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.028
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.027
And Tor is ready 9.672
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.936
After features/support/hooks.rb:339 0.705
After features/support/hooks.rb:108 0.000