Project Number Date
test_Tails_ISO_stable 6658 10 Sep 2026, 15:57

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:10.484 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.765
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.116
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.974
When I start Tails from USB drive "old" with network unplugged 48.184
Then the boot device has safe access rights 1.872
And Tails is running from USB drive "old" 0.195
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.169
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 1.778
After features/support/hooks.rb:108 0.005
Tags: @product
1:17.787
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 46.231
Then Tails is running from USB drive "old" 0.210
And I create a persistent partition 22.248
And I take note of which tps features are available 5.943
Then a Tails persistence partition exists on USB drive "old" 0.450
And I shutdown Tails and wait for the computer to power off 2.618
After features/support/hooks.rb:339 0.510
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.428
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.635
Then Tails is running from USB drive "old" 0.208
And all tps features are active 6.868
When I write some files expected to persist 0.948
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.147
And all persistence configuration files have safe access rights 0.243
And all persistent directories from the old Tails version have safe access rights 1.358
And I take note of which tps features are available 6.019
And I shutdown Tails and wait for the computer to power off 3.909
# 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.018
After features/support/hooks.rb:339 0.378
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.852
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.317
And I log in to a new session 11.259
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.688
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.650
Then the running Tails is installed on USB drive "to_upgrade" 17.455
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 1.524
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.033
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.545
Then all tps features from the old Tails version are active 1.001
And Tails is running from USB drive "to_upgrade" 0.177
And the boot device has safe access rights 1.934
And the expected persistent files created with the old Tails version are present in the filesystem 0.942
And all persistent directories from the old Tails version have safe access rights 1.345
After features/support/hooks.rb:339 0.634
After features/support/hooks.rb:108 0.005
3:30.671
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.057
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.170
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.308
When the network is plugged 0.032
And Tor is ready 12.688
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.524
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.673
Given I shutdown Tails and wait for the computer to power off 5.200
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.918
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.281
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.105
# 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.040
And Tor is ready 10.149
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.841
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.470
Given I shutdown Tails and wait for the computer to power off 2.544
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.789
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.539
And the file system changes introduced in version 6.3~testoverlayfs are present 0.307
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.110
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.161
When the network is plugged 0.032
And Tor is ready 9.975
Then the Upgrader considers the system as up-to-date 10.394
# 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.089
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.322
After features/support/hooks.rb:339 0.692
After features/support/hooks.rb:108 0.009
31.944
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 20.665
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
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.053
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.482
After features/support/hooks.rb:339 0.745
After features/support/hooks.rb:108 0.000