Project Number Date
test_Tails_ISO_devel 4578 31 Aug 2026, 11:16

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:32.700 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:5.418
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.973
When I start Tails from USB drive "old" with network unplugged 47.608
Then the boot device has safe access rights 1.971
And Tails is running from USB drive "old" 0.161
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 1.784
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.932
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.314
And I start Tails from USB drive "old" with network unplugged and I login 50.086
Then Tails is running from USB drive "old" 0.189
And I create a persistent partition 25.121
And I take note of which tps features are available 7.387
Then a Tails persistence partition exists on USB drive "old" 0.552
And I shutdown Tails and wait for the computer to power off 4.280
After features/support/hooks.rb:339 0.436
After features/support/hooks.rb:108 0.005
Tags: @product
1:35.707
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.273
Then Tails is running from USB drive "old" 0.241
And all tps features are active 7.567
When I write some files expected to persist 1.235
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 1.858
And I take note of which tps features are available 6.314
And I shutdown Tails and wait for the computer to power off 2.518
# 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.114
After features/support/hooks.rb:339 0.568
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.769
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.676
And I log in to a new session 12.163
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.731
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.032
Then the running Tails is installed on USB drive "to_upgrade" 19.678
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 3.847
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.453
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 1:4.558
Then all tps features from the old Tails version are active 1.095
And Tails is running from USB drive "to_upgrade" 0.181
And the boot device has safe access rights 2.036
And the expected persistent files created with the old Tails version are present in the filesystem 0.793
And all persistent directories from the old Tails version have safe access rights 1.698
After features/support/hooks.rb:339 0.788
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:39.381
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.773
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.025
And Tor is ready 13.346
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.040
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.587
Given I shutdown Tails and wait for the computer to power off 6.781
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.833
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 9.000
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.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.100
# 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.178
When the network is plugged 0.026
And Tor is ready 10.443
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.886
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.247
Given I shutdown Tails and wait for the computer to power off 4.157
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.290
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.296
And the file system changes introduced in version 6.3~testoverlayfs are present 0.402
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.126
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.026
And Tor is ready 10.446
Then the Upgrader considers the system as up-to-date 0.100
# 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.269
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.365
After features/support/hooks.rb:339 1.057
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.037
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.320
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.430
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.898
After features/support/hooks.rb:339 0.670
After features/support/hooks.rb:108 0.000