Project Number Date
test_Tails_ISO_stable 6418 02 Jun 2026, 18:22

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:12.919 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:10.835
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.098
When I start Tails from USB drive "old" with network unplugged 53.362
Then the boot device has safe access rights 2.660
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:335 1.248
After features/support/hooks.rb:104 0.006
Tags: @product
1:26.435
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 52.943
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 24.444
And I take note of which tps features are available 0.311
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 7.932
After features/support/hooks.rb:335 0.424
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.152
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.363
Then Tails is running from USB drive "old" 0.258
And all tps features are active 1.142
When I write some files expected to persist 1.238
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.271
And all persistent directories from the old Tails version have safe access rights 1.833
And I take note of which tps features are available 0.142
And I shutdown Tails and wait for the computer to power off 7.814
# 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.867
After features/support/hooks.rb:335 0.208
After features/support/hooks.rb:104 0.006
Tags: @product
2:8.330
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.026
And I log in to a new session 12.501
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.667
And I plug USB drive "to_upgrade" 2.216
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.209
Then the running Tails is installed on USB drive "to_upgrade" 13.443
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:335 2.215
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.728
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.785
Then all tps features from the old Tails version are active 1.037
And Tails is running from USB drive "to_upgrade" 0.191
And the boot device has safe access rights 2.461
And the expected persistent files created with the old Tails version are present in the filesystem 1.155
And all persistent directories from the old Tails version have safe access rights 2.034
After features/support/hooks.rb:335 0.517
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:34.950
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.048
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.344
When the network is plugged 0.020
And Tor is ready 13.062
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.336
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.518
Given I shutdown Tails and wait for the computer to power off 9.441
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.864
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.033
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.163
When the network is plugged 0.014
And Tor is ready 9.698
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.723
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.082
Given I shutdown Tails and wait for the computer to power off 8.129
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.605
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.147
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.043
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.208
When the network is plugged 0.013
And Tor is ready 10.036
Then the Upgrader considers the system as up-to-date 10.556
# 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.898
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.375
After features/support/hooks.rb:335 1.048
After features/support/hooks.rb:104 0.048
Tags: @product @automatic_upgrade
20.487
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.173
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
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.077
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.887
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.050
After features/support/hooks.rb:335 0.703
After features/support/hooks.rb:104 0.000