Project Number Date
test_Tails_ISO_stable 6383 18 May 2026, 11:26

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:30.846 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:5.639
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.009
Given a computer 0.053
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.734
When I start Tails from USB drive "old" with network unplugged 47.087
Then the boot device has safe access rights 3.051
And Tails is running from USB drive "old" 0.271
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.159
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:335 1.272
After features/support/hooks.rb:104 0.008
Tags: @product
1:29.363
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.115
And I start Tails from USB drive "old" with network unplugged and I login 55.431
Then Tails is running from USB drive "old" 0.246
And I create a persistent partition 25.813
And I take note of which tps features are available 0.351
Then a Tails persistence partition exists on USB drive "old" 0.541
And I shutdown Tails and wait for the computer to power off 6.864
After features/support/hooks.rb:335 0.560
After features/support/hooks.rb:104 0.006
Tags: @product
1:29.520
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.225
Then Tails is running from USB drive "old" 0.262
And all tps features are active 1.096
When I write some files expected to persist 1.313
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.343
And all persistent directories from the old Tails version have safe access rights 2.089
And I take note of which tps features are available 0.180
And I shutdown Tails and wait for the computer to power off 8.397
# 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.384
After features/support/hooks.rb:335 0.336
After features/support/hooks.rb:104 0.008
Tags: @product
2:10.720
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 without a persistent partition and stopped at Tails Greeter's login screen 7.998
And I log in to a new session 12.825
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.797
And I plug USB drive "to_upgrade" 2.257
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.430
Then the running Tails is installed on USB drive "to_upgrade" 15.140
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:335 0.620
After features/support/hooks.rb:104 0.000
Tags: @product
1:12.210
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.063
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.129
Then all tps features from the old Tails version are active 0.973
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 2.888
And the expected persistent files created with the old Tails version are present in the filesystem 1.490
And all persistent directories from the old Tails version have safe access rights 2.300
After features/support/hooks.rb:335 0.526
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:43.456
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 with a persistent partition enabled and logged in 8.364
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
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.239
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.015
And Tor is ready 13.483
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.797
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.743
Given I shutdown Tails and wait for the computer to power off 9.663
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.124
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.158
And the file system changes introduced in version 6.2~testoverlayfs are present 0.240
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.210
When the network is plugged 0.014
And Tor is ready 9.997
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.972
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.708
Given I shutdown Tails and wait for the computer to power off 8.119
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.661
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.286
And the file system changes introduced in version 6.3~testoverlayfs are present 0.370
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.014
And Tor is ready 11.568
Then the Upgrader considers the system as up-to-date 10.562
# 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.337
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.351
After features/support/hooks.rb:335 1.010
After features/support/hooks.rb:104 0.018
Tags: @product @automatic_upgrade
19.935
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.593
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
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.015
And Tor is ready 10.186
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.817
After features/support/hooks.rb:335 0.837
After features/support/hooks.rb:104 0.000