Project Number Date
test_Tails_ISO_stable 6321 22 Apr 2026, 10:36

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 12:10.900 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:2.594
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.061
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.061
When I start Tails from USB drive "old" with network unplugged 45.139
Then the boot device has safe access rights 2.678
And Tails is running from USB drive "old" 0.195
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:331 1.153
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.791
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 53.105
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 23.325
And I take note of which tps features are available 0.648
Then a Tails persistence partition exists on USB drive "old" 0.507
And I shutdown Tails and wait for the computer to power off 7.881
After features/support/hooks.rb:331 0.541
After features/support/hooks.rb:100 0.007
Tags: @product
1:26.132
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.644
Then Tails is running from USB drive "old" 0.234
And all tps features are active 1.128
When I write some files expected to persist 1.381
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.474
And all persistent directories from the old Tails version have safe access rights 1.908
And I take note of which tps features are available 0.165
And I shutdown Tails and wait for the computer to power off 7.924
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.016
After features/support/hooks.rb:331 0.222
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.620
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 7.735
And I log in to a new session 12.155
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.764
And I plug USB drive "to_upgrade" 2.243
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.171
Then the running Tails is installed on USB drive "to_upgrade" 15.257
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.161
After features/support/hooks.rb:331 3.506
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.635
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
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.994
Then all tps features from the old Tails version are active 1.019
And Tails is running from USB drive "to_upgrade" 0.260
And the boot device has safe access rights 2.506
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.721
After features/support/hooks.rb:331 0.638
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:33.877
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.133
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.221
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.365
When the network is plugged 0.018
And Tor is ready 20.335
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.408
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.699
Given I shutdown Tails and wait for the computer to power off 20.042
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.735
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.106
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.192
When the network is plugged 0.017
And Tor is ready 19.999
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.345
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.454
Given I shutdown Tails and wait for the computer to power off 17.068
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.509
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.168
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.212
When the network is plugged 0.014
And Tor is ready 21.569
Then the Upgrader considers the system as up-to-date 0.099
# 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.403
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.448
After features/support/hooks.rb:331 1.070
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
25.250
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.450
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 17.049
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.372
After features/support/hooks.rb:331 0.952
After features/support/hooks.rb:100 0.000