Project Number Date
test_Tails_ISO_devel 4545 13 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:36.406 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:14.680
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.097
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.049
When I start Tails from USB drive "old" with network unplugged 57.775
Then the boot device has safe access rights 2.145
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.154
And I unplug USB drive "old" 0.105
After features/support/hooks.rb:339 1.460
After features/support/hooks.rb:108 0.007
Tags: @product
1:20.472
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 46.931
Then Tails is running from USB drive "old" 0.185
And I create a persistent partition 23.837
And I take note of which tps features are available 6.316
Then a Tails persistence partition exists on USB drive "old" 0.484
And I shutdown Tails and wait for the computer to power off 2.633
After features/support/hooks.rb:339 0.435
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.805
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.450
Then Tails is running from USB drive "old" 0.186
And all tps features are active 7.709
When I write some files expected to persist 1.096
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.292
And all persistent directories from the old Tails version have safe access rights 1.824
And I take note of which tps features are available 5.722
And I shutdown Tails and wait for the computer to power off 2.592
# 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.692
After features/support/hooks.rb:339 0.464
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.930
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.042
And I log in to a new session 12.124
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.706
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.027
Then the running Tails is installed on USB drive "to_upgrade" 18.559
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:339 3.718
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.198
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.942
Then all tps features from the old Tails version are active 1.128
And Tails is running from USB drive "to_upgrade" 0.210
And the boot device has safe access rights 2.240
And the expected persistent files created with the old Tails version are present in the filesystem 0.967
And all persistent directories from the old Tails version have safe access rights 1.629
After features/support/hooks.rb:339 0.493
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
3:49.264
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.266
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.191
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.216
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.316
When the network is plugged 0.038
And Tor is ready 11.978
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.610
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.938
Given I shutdown Tails and wait for the computer to power off 5.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.587
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.978
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.095
# 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.169
When the network is plugged 0.031
And Tor is ready 18.809
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.310
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.754
Given I shutdown Tails and wait for the computer to power off 2.613
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.357
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.741
And the file system changes introduced in version 6.3~testoverlayfs are present 0.367
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.028
And Tor is ready 10.213
Then the Upgrader considers the system as up-to-date 10.489
# 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.575
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.371
After features/support/hooks.rb:339 1.056
After features/support/hooks.rb:108 0.061
Tags: @product @automatic_upgrade
19.055
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 7.926
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.187
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.050
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 10.447
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.367
After features/support/hooks.rb:339 0.626
After features/support/hooks.rb:108 0.000