Project Number Date
test_Tails_ISO_stable 6663 14 Sep 2026, 11:41

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.291 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:13.413
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.527
When I start Tails from USB drive "old" with network unplugged 56.078
Then the boot device has safe access rights 2.112
And Tails is running from USB drive "old" 0.186
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.169
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 1.676
After features/support/hooks.rb:108 0.007
Tags: @product
1:24.098
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 48.904
Then Tails is running from USB drive "old" 0.226
And I create a persistent partition 22.849
And I take note of which tps features are available 7.557
Then a Tails persistence partition exists on USB drive "old" 0.498
And I shutdown Tails and wait for the computer to power off 3.974
After features/support/hooks.rb:339 0.235
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.467
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.756
Then Tails is running from USB drive "old" 0.220
And all tps features are active 7.735
When I write some files expected to persist 1.193
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.317
And all persistent directories from the old Tails version have safe access rights 1.696
And I take note of which tps features are available 5.752
And I shutdown Tails and wait for the computer to power off 3.945
# 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.598
After features/support/hooks.rb:339 0.338
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.591
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.246
And I log in to a new session 11.331
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.603
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.436
Then the running Tails is installed on USB drive "to_upgrade" 18.512
And I unplug USB drive "to_upgrade" 0.105
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 1.812
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.358
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.105
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.084
Then all tps features from the old Tails version are active 1.525
And Tails is running from USB drive "to_upgrade" 0.214
And the boot device has safe access rights 2.144
And the expected persistent files created with the old Tails version are present in the filesystem 0.782
And all persistent directories from the old Tails version have safe access rights 1.501
After features/support/hooks.rb:339 0.833
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:41.335
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 21.478
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.026
And Tor is ready 11.843
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.198
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.755
Given I shutdown Tails and wait for the computer to power off 5.459
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.009
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.690
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.087
# 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.180
When the network is plugged 0.035
And Tor is ready 10.262
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.507
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.846
Given I shutdown Tails and wait for the computer to power off 4.190
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.589
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.461
And the file system changes introduced in version 6.3~testoverlayfs are present 0.377
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186
When the network is plugged 0.044
And Tor is ready 10.156
Then the Upgrader considers the system as up-to-date 0.094
# 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.116
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.363
After features/support/hooks.rb:339 0.919
After features/support/hooks.rb:108 0.034
Tags: @product @automatic_upgrade
20.024
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.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
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.043
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 9.480
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.160
After features/support/hooks.rb:339 0.666
After features/support/hooks.rb:108 0.000