Project Number Date
test_Tails_ISO_stable 6719 03 Oct 2026, 11:24

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 10:41.967 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:7.283
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.383
When I start Tails from USB drive "old" with network unplugged 50.342
Then the boot device has safe access rights 1.863
And Tails is running from USB drive "old" 0.196
And there is no persistence partition on USB drive "old" 0.031
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.168
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.773
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.467
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login 46.157
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 22.585
And I take note of which tps features are available 5.780
Then a Tails persistence partition exists on USB drive "old" 0.567
And I shutdown Tails and wait for the computer to power off 4.049
After features/support/hooks.rb:339 0.393
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.636
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.551
Then Tails is running from USB drive "old" 0.236
And all tps features are active 6.766
When I write some files expected to persist 0.975
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.126
And all persistence configuration files have safe access rights 0.231
And all persistent directories from the old Tails version have safe access rights 1.309
And I take note of which tps features are available 5.644
And I shutdown Tails and wait for the computer to power off 2.666
# 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.041
After features/support/hooks.rb:339 0.164
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.326
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.127
And I log in to a new session 9.823
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.658
And I plug USB drive "to_upgrade" 2.187
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.975
Then the running Tails is installed on USB drive "to_upgrade" 17.315
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 1.705
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.393
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 57.797
Then all tps features from the old Tails version are active 0.997
And Tails is running from USB drive "to_upgrade" 0.140
And the boot device has safe access rights 1.812
And the expected persistent files created with the old Tails version are present in the filesystem 1.070
And all persistent directories from the old Tails version have safe access rights 1.503
After features/support/hooks.rb:339 0.777
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:18.448
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.855
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.189
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.156
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.285
When the network is plugged 0.041
And Tor is ready 12.902
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.298
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.010
Given I shutdown Tails and wait for the computer to power off 5.507
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.511
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.270
And the file system changes introduced in version 6.2~testoverlayfs are present 0.149
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.115
# 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.159
When the network is plugged 0.024
And Tor is ready 9.949
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.510
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.193
Given I shutdown Tails and wait for the computer to power off 2.589
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.933
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.417
And the file system changes introduced in version 6.3~testoverlayfs are present 0.226
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.108
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.156
When the network is plugged 0.024
And Tor is ready 10.058
Then the Upgrader considers the system as up-to-date 0.122
# 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.113
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.328
After features/support/hooks.rb:339 0.986
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
17.410
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.606
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.183
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 8.129
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.352
After features/support/hooks.rb:339 0.745
After features/support/hooks.rb:108 0.000