Project Number Date
test_Tails_ISO_stable 6404 26 May 2026, 11:31

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:14.732 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:1.653
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.067
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.650
When I start Tails from USB drive "old" with network unplugged 43.198
Then the boot device has safe access rights 2.863
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.244
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:335 3.449
After features/support/hooks.rb:104 0.006
Tags: @product
1:28.376
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 53.708
Then Tails is running from USB drive "old" 0.259
And I create a persistent partition 25.417
And I take note of which tps features are available 0.341
Then a Tails persistence partition exists on USB drive "old" 0.619
And I shutdown Tails and wait for the computer to power off 7.978
After features/support/hooks.rb:335 0.471
After features/support/hooks.rb:104 0.006
Tags: @product
1:22.063
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 with persistence enabled 1:0.237
Then Tails is running from USB drive "old" 0.220
And all tps features are active 1.106
When I write some files expected to persist 1.303
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.363
And all persistent directories from the old Tails version have safe access rights 1.925
And I take note of which tps features are available 0.158
And I shutdown Tails and wait for the computer to power off 4.311
# 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.144
After features/support/hooks.rb:335 0.233
After features/support/hooks.rb:104 0.007
Tags: @product
2:10.055
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.908
And I log in to a new session 12.513
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.824
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.311
Then the running Tails is installed on USB drive "to_upgrade" 14.925
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.185
After features/support/hooks.rb:335 2.080
After features/support/hooks.rb:104 0.000
Tags: @product
1:9.670
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.607
Then all tps features from the old Tails version are active 0.991
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 2.521
And the expected persistent files created with the old Tails version are present in the filesystem 1.102
And all persistent directories from the old Tails version have safe access rights 2.061
After features/support/hooks.rb:335 0.702
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:40.261
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.507
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
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.362
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.420
When the network is plugged 0.024
And Tor is ready 12.460
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.138
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.025
Given I shutdown Tails and wait for the computer to power off 6.847
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.191
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.188
And the file system changes introduced in version 6.2~testoverlayfs are present 0.260
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.189
# 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.347
When the network is plugged 0.014
And Tor is ready 11.299
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.754
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.404
Given I shutdown Tails and wait for the computer to power off 8.145
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.845
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.117
And the file system changes introduced in version 6.3~testoverlayfs are present 0.359
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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.014
And Tor is ready 10.305
Then the Upgrader considers the system as up-to-date 10.504
# 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.250
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.431
After features/support/hooks.rb:335 0.773
After features/support/hooks.rb:104 0.034
Tags: @product @automatic_upgrade
22.650
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.361
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
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.049
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.268
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.600
After features/support/hooks.rb:335 0.546
After features/support/hooks.rb:104 0.000