Project Number Date
test_Tails_ISO_stable 6257 02 Apr 2026, 11:08

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 13:15.536 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:18.368
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.133
When I start Tails from USB drive "old" with network unplugged 59.615
Then the boot device has safe access rights 2.833
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:331 3.813
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.660
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login 55.752
Then Tails is running from USB drive "old" 0.262
And I create a persistent partition 25.519
And I take note of which tps features are available 1.095
Then a Tails persistence partition exists on USB drive "old" 0.621
And I shutdown Tails and wait for the computer to power off 8.342
After features/support/hooks.rb:331 0.205
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.973
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.120
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.476
Then Tails is running from USB drive "old" 0.268
And all tps features are active 1.277
When I write some files expected to persist 1.415
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.461
And all persistent directories from the old Tails version have safe access rights 2.091
And I take note of which tps features are available 0.183
And I shutdown Tails and wait for the computer to power off 8.319
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.111
After features/support/hooks.rb:331 0.476
After features/support/hooks.rb:100 0.022
Tags: @product
2:15.207
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.098
And I log in to a new session 13.277
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.762
And I plug USB drive "to_upgrade" 2.248
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.653
Then the running Tails is installed on USB drive "to_upgrade" 16.902
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:331 2.621
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.284
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.110
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.624
Then all tps features from the old Tails version are active 1.056
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.831
And the expected persistent files created with the old Tails version are present in the filesystem 1.270
And all persistent directories from the old Tails version have safe access rights 2.134
After features/support/hooks.rb:331 0.955
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
4:38.920
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 with a persistent partition enabled and logged in 8.057
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.019
And Tor is ready 20.650
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.378
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.649
Given I shutdown Tails and wait for the computer to power off 20.329
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.665
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.389
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.235
When the network is plugged 0.038
And Tor is ready 20.268
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.399
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.277
Given I shutdown Tails and wait for the computer to power off 17.495
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.925
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.346
And the file system changes introduced in version 6.3~testoverlayfs are present 0.399
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.014
And Tor is ready 20.459
Then the Upgrader considers the system as up-to-date 0.093
# 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.367
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:331 1.011
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
49.121
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 with a persistent partition enabled and logged in 7.270
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
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.016
And Tor is ready 41.152
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.349
After features/support/hooks.rb:331 0.619
After features/support/hooks.rb:100 0.000