Project Number Date
test_Tails_ISO_stable 6080 20 Jan 2026, 08:20

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:25.227 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:9.975
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.070
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.358
When I start Tails from USB drive "old" with network unplugged 50.293
Then the boot device has safe access rights 3.362
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.265
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 3.917
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.404
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login 54.219
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 24.494
And I take note of which tps features are available 0.727
Then a Tails persistence partition exists on USB drive "old" 0.500
And I shutdown Tails and wait for the computer to power off 4.040
After features/support/hooks.rb:331 0.461
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.156
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.654
Then Tails is running from USB drive "old" 0.281
And all tps features are active 1.098
When I write some files expected to persist 1.461
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.150
And all persistence configuration files have safe access rights 0.301
And all persistent directories from the old Tails version have safe access rights 2.381
And I take note of which tps features are available 0.180
And I shutdown Tails and wait for the computer to power off 4.171
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.411
After features/support/hooks.rb:331 0.203
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.077
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.710
And I log in to a new session 10.068
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.888
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.435
Then the running Tails is installed on USB drive "to_upgrade" 16.452
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 3.574
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.002
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.274
Then all tps features from the old Tails version are active 0.890
And Tails is running from USB drive "to_upgrade" 0.298
And the boot device has safe access rights 2.976
And the expected persistent files created with the old Tails version are present in the filesystem 1.392
And all persistent directories from the old Tails version have safe access rights 2.110
After features/support/hooks.rb:331 0.767
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:43.347
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 8.376
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
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.383
When the network is plugged 0.017
And Tor is ready 14.537
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.966
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.655
Given I shutdown Tails and wait for the computer to power off 9.934
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.316
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.084
And the file system changes introduced in version 6.2~testoverlayfs are present 0.188
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.120
# 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.204
When the network is plugged 0.017
And Tor is ready 9.971
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.415
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.277
Given I shutdown Tails and wait for the computer to power off 7.932
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.928
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.318
And the file system changes introduced in version 6.3~testoverlayfs are present 0.417
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.178
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.372
When the network is plugged 0.017
And Tor is ready 9.936
Then the Upgrader considers the system as up-to-date 10.503
# 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.146
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.348
After features/support/hooks.rb:331 0.651
After features/support/hooks.rb:100 0.046
Tags: @product @automatic_upgrade
19.263
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 7.506
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
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.018
And Tor is ready 10.268
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.171
After features/support/hooks.rb:331 0.961
After features/support/hooks.rb:100 0.000