Project Number Date
test_Tails_ISO_devel 4468 25 Jun 2026, 11:12

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:26.744 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
59.644
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.329
When I start Tails from USB drive "old" with network unplugged 41.871
Then the boot device has safe access rights 2.645
And Tails is running from USB drive "old" 0.249
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.202
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.465
After features/support/hooks.rb:108 0.007
Tags: @product
1:28.589
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 52.370
Then Tails is running from USB drive "old" 0.245
And I create a persistent partition 23.527
And I take note of which tps features are available 3.626
Then a Tails persistence partition exists on USB drive "old" 0.487
And I shutdown Tails and wait for the computer to power off 8.280
After features/support/hooks.rb:339 0.289
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.220
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.037
Then Tails is running from USB drive "old" 0.241
And all tps features are active 4.907
When I write some files expected to persist 1.218
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.251
And all persistent directories from the old Tails version have safe access rights 1.775
And I take note of which tps features are available 3.858
And I shutdown Tails and wait for the computer to power off 3.982
# 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.707
After features/support/hooks.rb:339 0.148
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.685
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.164
And I log in to a new session 12.956
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.862
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.105
Then the running Tails is installed on USB drive "to_upgrade" 15.100
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:339 2.348
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.491
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.893
Then all tps features from the old Tails version are active 0.913
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 2.290
And the expected persistent files created with the old Tails version are present in the filesystem 1.206
And all persistent directories from the old Tails version have safe access rights 1.903
After features/support/hooks.rb:339 0.761
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:45.428
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.238
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.334
When the network is plugged 0.017
And Tor is ready 11.816
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.473
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.518
Given I shutdown Tails and wait for the computer to power off 9.291
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.704
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.735
And the file system changes introduced in version 6.2~testoverlayfs are present 0.216
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.244
When the network is plugged 0.018
And Tor is ready 10.591
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.871
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.403
Given I shutdown Tails and wait for the computer to power off 7.937
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.742
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.624
And the file system changes introduced in version 6.3~testoverlayfs are present 0.387
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.018
And Tor is ready 9.813
Then the Upgrader considers the system as up-to-date 10.551
# 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.220
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.423
After features/support/hooks.rb:339 0.925
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
20.684
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.460
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.795
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.083
After features/support/hooks.rb:339 0.544
After features/support/hooks.rb:108 0.000