Project Number Date
test_Tails_ISO_devel 4428 03 Jun 2026, 11:28

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:14.028 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:17.676
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.057
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.250
When I start Tails from USB drive "old" with network unplugged 1:0.162
Then the boot device has safe access rights 2.544
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.032
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:335 3.432
After features/support/hooks.rb:104 0.006
Tags: @product
1:23.871
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 51.782
Then Tails is running from USB drive "old" 0.257
And I create a persistent partition 24.005
And I take note of which tps features are available 0.312
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 6.918
After features/support/hooks.rb:335 0.504
After features/support/hooks.rb:104 0.007
Tags: @product
1:21.750
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.482
Then Tails is running from USB drive "old" 0.216
And all tps features are active 1.270
When I write some files expected to persist 1.192
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.277
And all persistent directories from the old Tails version have safe access rights 1.984
And I take note of which tps features are available 0.145
And I shutdown Tails and wait for the computer to power off 4.124
# 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.828
After features/support/hooks.rb:335 0.608
After features/support/hooks.rb:104 0.006
Tags: @product
2:9.413
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.024
And I log in to a new session 11.589
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.848
And I plug USB drive "to_upgrade" 2.247
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.487
Then the running Tails is installed on USB drive "to_upgrade" 14.929
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:335 2.063
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.271
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.402
Then all tps features from the old Tails version are active 1.032
And Tails is running from USB drive "to_upgrade" 0.243
And the boot device has safe access rights 2.518
And the expected persistent files created with the old Tails version are present in the filesystem 1.243
And all persistent directories from the old Tails version have safe access rights 1.784
After features/support/hooks.rb:335 1.052
After features/support/hooks.rb:104 0.006
3:35.010
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.120
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.196
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.342
When the network is plugged 0.019
And Tor is ready 13.184
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.695
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.071
Given I shutdown Tails and wait for the computer to power off 6.908
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.467
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.138
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.218
When the network is plugged 0.022
And Tor is ready 11.528
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.094
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.374
Given I shutdown Tails and wait for the computer to power off 7.965
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.101
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.014
And the file system changes introduced in version 6.3~testoverlayfs are present 0.314
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.182
When the network is plugged 0.018
And Tor is ready 11.013
Then the Upgrader considers the system as up-to-date 10.544
# 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.133
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.359
After features/support/hooks.rb:335 0.880
After features/support/hooks.rb:104 0.010
20.033
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.434
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.038
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 11.226
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.026
After features/support/hooks.rb:335 0.780
After features/support/hooks.rb:104 0.000