Project Number Date
test_Tails_ISO_stable 6406 27 May 2026, 11:43

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:6.402 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:11.758
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.364
When I start Tails from USB drive "old" with network unplugged 52.273
Then the boot device has safe access rights 3.250
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:335 3.817
After features/support/hooks.rb:104 0.006
Tags: @product
1:32.542
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 58.226
Then Tails is running from USB drive "old" 0.218
And I create a persistent partition 24.960
And I take note of which tps features are available 0.329
Then a Tails persistence partition exists on USB drive "old" 0.536
And I shutdown Tails and wait for the computer to power off 8.195
After features/support/hooks.rb:335 0.381
After features/support/hooks.rb:104 0.007
Tags: @product
1:33.115
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:6.365
Then Tails is running from USB drive "old" 0.274
And all tps features are active 1.237
When I write some files expected to persist 1.591
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.272
And all persistence configuration files have safe access rights 0.330
And all persistent directories from the old Tails version have safe access rights 2.094
And I take note of which tps features are available 0.200
And I shutdown Tails and wait for the computer to power off 8.115
# 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.559
After features/support/hooks.rb:335 0.249
After features/support/hooks.rb:104 0.006
Tags: @product
2:17.168
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.546
And I log in to a new session 15.001
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.866
And I plug USB drive "to_upgrade" 2.286
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.248
Then the running Tails is installed on USB drive "to_upgrade" 17.926
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.151
After features/support/hooks.rb:335 2.189
After features/support/hooks.rb:104 0.000
Tags: @product
1:16.404
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.087
Then all tps features from the old Tails version are active 1.415
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.165
And the expected persistent files created with the old Tails version are present in the filesystem 1.388
And all persistent directories from the old Tails version have safe access rights 1.968
After features/support/hooks.rb:335 0.872
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:54.081
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.362
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.551
When the network is plugged 0.017
And Tor is ready 12.804
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.646
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.628
Given I shutdown Tails and wait for the computer to power off 9.731
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.825
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.339
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.264
When the network is plugged 0.016
And Tor is ready 10.298
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.681
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.490
Given I shutdown Tails and wait for the computer to power off 8.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.531
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.354
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.053
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.016
And Tor is ready 11.792
Then the Upgrader considers the system as up-to-date 10.627
# 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.466
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.352
After features/support/hooks.rb:335 1.057
After features/support/hooks.rb:104 0.013
Tags: @product @automatic_upgrade
21.331
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 7.793
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.437
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.748
After features/support/hooks.rb:335 0.954
After features/support/hooks.rb:104 0.000