Project Number Date
test_Tails_ISO_devel 4484 07 Jul 2026, 11:11

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:36.908 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.052
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.215
When I start Tails from USB drive "old" with network unplugged 47.565
Then the boot device has safe access rights 2.524
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.679
After features/support/hooks.rb:108 0.007
Tags: @product
1:28.570
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.132
And I start Tails from USB drive "old" with network unplugged and I login 50.953
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 24.707
And I take note of which tps features are available 3.920
Then a Tails persistence partition exists on USB drive "old" 0.553
And I shutdown Tails and wait for the computer to power off 8.055
After features/support/hooks.rb:339 0.325
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.042
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.923
Then Tails is running from USB drive "old" 0.270
And all tps features are active 4.796
When I write some files expected to persist 1.350
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 1.933
And I take note of which tps features are available 3.596
And I shutdown Tails and wait for the computer to power off 7.901
# 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.673
After features/support/hooks.rb:339 0.327
After features/support/hooks.rb:108 0.009
Tags: @product
2:7.945
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 7.625
And I log in to a new session 12.059
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.779
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.234
Then the running Tails is installed on USB drive "to_upgrade" 13.765
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 1.798
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.424
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.629
Then all tps features from the old Tails version are active 0.939
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.457
And the expected persistent files created with the old Tails version are present in the filesystem 1.124
And all persistent directories from the old Tails version have safe access rights 1.948
After features/support/hooks.rb:339 0.865
After features/support/hooks.rb:108 0.005
3:50.533
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 7.851
And no SquashFS delta is installed 0.047
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
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.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.019
And Tor is ready 11.962
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.732
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.641
Given I shutdown Tails and wait for the computer to power off 9.370
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.995
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.028
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.169
# 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.205
When the network is plugged 0.017
And Tor is ready 10.623
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.303
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.181
Given I shutdown Tails and wait for the computer to power off 8.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.477
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.537
And the file system changes introduced in version 6.3~testoverlayfs are present 0.302
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.020
And Tor is ready 10.068
Then the Upgrader considers the system as up-to-date 10.511
# 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.287
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.343
After features/support/hooks.rb:339 0.892
After features/support/hooks.rb:108 0.010
19.338
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 7.396
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.043
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 9.168
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.453
After features/support/hooks.rb:339 0.845
After features/support/hooks.rb:108 0.000