Project Number Date
test_Tails_ISO_devel 4340 14 Apr 2026, 11:08

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:15.078 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.104
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.065
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 13.765
When I start Tails from USB drive "old" with network unplugged 50.445
Then the boot device has safe access rights 3.053
And Tails is running from USB drive "old" 0.250
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:331 3.480
After features/support/hooks.rb:100 0.008
Tags: @product
1:30.979
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 55.606
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 25.260
And I take note of which tps features are available 0.857
Then a Tails persistence partition exists on USB drive "old" 0.589
And I shutdown Tails and wait for the computer to power off 8.276
After features/support/hooks.rb:331 0.470
After features/support/hooks.rb:100 0.008
Tags: @product
1:33.307
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.886
Then Tails is running from USB drive "old" 0.314
And all tps features are active 1.346
When I write some files expected to persist 1.676
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.288
And all persistence configuration files have safe access rights 0.629
And all persistent directories from the old Tails version have safe access rights 2.272
And I take note of which tps features are available 0.312
And I shutdown Tails and wait for the computer to power off 8.419
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.084
After features/support/hooks.rb:331 0.538
After features/support/hooks.rb:100 0.008
Tags: @product
2:13.461
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.071
And I log in to a new session 12.592
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.801
And I plug USB drive "to_upgrade" 2.238
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.086
Then the running Tails is installed on USB drive "to_upgrade" 16.352
And I unplug USB drive "to_upgrade" 0.166
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:331 2.274
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.171
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.124
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.433
Then all tps features from the old Tails version are active 1.116
And Tails is running from USB drive "to_upgrade" 0.296
And the boot device has safe access rights 2.849
And the expected persistent files created with the old Tails version are present in the filesystem 1.293
And all persistent directories from the old Tails version have safe access rights 2.056
After features/support/hooks.rb:331 0.577
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
5:8.991
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.925
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.559
When the network is plugged 0.031
And Tor is ready 21.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.425
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.597
Given I shutdown Tails and wait for the computer to power off 21.005
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.654
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.102
And the file system changes introduced in version 6.2~testoverlayfs are present 0.250
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.230
When the network is plugged 0.020
And Tor is ready 20.826
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.394
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.757
Given I shutdown Tails and wait for the computer to power off 17.394
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.782
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.128
And the file system changes introduced in version 6.3~testoverlayfs are present 0.329
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.189
When the network is plugged 0.015
And Tor is ready 40.271
Then the Upgrader considers the system as up-to-date 0.126
# 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.868
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.406
After features/support/hooks.rb:331 1.027
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
27.061
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.752
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 18.540
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.401
After features/support/hooks.rb:331 0.793
After features/support/hooks.rb:100 0.000