Project Number Date
test_Tails_ISO_stable 6426 03 Jun 2026, 15:34

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.770 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
59.880
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.061
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 13.706
When I start Tails from USB drive "old" with network unplugged 41.503
Then the boot device has safe access rights 2.769
And Tails is running from USB drive "old" 0.262
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.160
After features/support/hooks.rb:335 1.402
After features/support/hooks.rb:104 0.015
Tags: @product
1:28.983
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 54.189
Then Tails is running from USB drive "old" 0.275
And I create a persistent partition 25.223
And I take note of which tps features are available 0.438
Then a Tails persistence partition exists on USB drive "old" 0.657
And I shutdown Tails and wait for the computer to power off 8.111
After features/support/hooks.rb:335 0.409
After features/support/hooks.rb:104 0.007
Tags: @product
1:30.114
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.320
Then Tails is running from USB drive "old" 0.275
And all tps features are active 1.307
When I write some files expected to persist 1.294
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.284
And all persistent directories from the old Tails version have safe access rights 2.191
And I take note of which tps features are available 0.197
And I shutdown Tails and wait for the computer to power off 8.396
# 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" 12.576
After features/support/hooks.rb:335 0.192
After features/support/hooks.rb:104 0.025
Tags: @product
2:12.181
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.236
And I log in to a new session 12.990
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.832
And I plug USB drive "to_upgrade" 2.336
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.829
Then the running Tails is installed on USB drive "to_upgrade" 15.697
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:335 0.947
After features/support/hooks.rb:104 0.000
Tags: @product
1:12.983
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.895
Then all tps features from the old Tails version are active 1.257
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 2.926
And the expected persistent files created with the old Tails version are present in the filesystem 1.290
And all persistent directories from the old Tails version have safe access rights 2.244
After features/support/hooks.rb:335 0.853
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:47.457
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.264
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.400
When the network is plugged 0.016
And Tor is ready 12.636
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.985
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.308
Given I shutdown Tails and wait for the computer to power off 10.047
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.051
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.183
And the file system changes introduced in version 6.2~testoverlayfs are present 0.203
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.255
When the network is plugged 0.020
And Tor is ready 11.537
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.605
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.101
Given I shutdown Tails and wait for the computer to power off 8.160
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.016
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.250
And the file system changes introduced in version 6.3~testoverlayfs are present 0.395
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.015
And Tor is ready 10.381
Then the Upgrader considers the system as up-to-date 10.598
# 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.336
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.417
After features/support/hooks.rb:335 0.973
After features/support/hooks.rb:104 0.016
Tags: @product @automatic_upgrade
21.169
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.947
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 9.549
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.307
After features/support/hooks.rb:335 0.533
After features/support/hooks.rb:104 0.000