Project Number Date
test_Tails_ISO_stable 6036 05 Jan 2026, 17:19

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:18.083 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:20.316
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.964
When I start Tails from USB drive "old" with network unplugged 1:1.411
Then the boot device has safe access rights 2.752
And Tails is running from USB drive "old" 0.272
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.338
After features/support/hooks.rb:331 3.982
After features/support/hooks.rb:100 0.025
Tags: @product
1:31.301
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login 55.586
Then Tails is running from USB drive "old" 0.437
And I create a persistent partition 25.382
And I take note of which tps features are available 0.781
Then a Tails persistence partition exists on USB drive "old" 0.674
And I shutdown Tails and wait for the computer to power off 8.373
After features/support/hooks.rb:331 0.641
After features/support/hooks.rb:100 0.018
Tags: @product
1:27.329
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.828
Then Tails is running from USB drive "old" 0.389
And all tps features are active 1.503
When I write some files expected to persist 1.467
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.149
And I take note of which tps features are available 0.173
And I shutdown Tails and wait for the computer to power off 4.176
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.934
After features/support/hooks.rb:331 0.543
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.114
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 8.956
And I log in to a new session 13.961
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.842
And I plug USB drive "to_upgrade" 2.331
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.787
Then the running Tails is installed on USB drive "to_upgrade" 16.930
And I unplug USB drive "to_upgrade" 0.164
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:331 3.812
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.055
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.126
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.097
Then all tps features from the old Tails version are active 1.098
And Tails is running from USB drive "to_upgrade" 0.260
And the boot device has safe access rights 3.019
And the expected persistent files created with the old Tails version are present in the filesystem 1.295
And all persistent directories from the old Tails version have safe access rights 2.158
After features/support/hooks.rb:331 0.844
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:10.185
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.603
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.024
And Tor is ready 12.802
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.777
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.156
Given I shutdown Tails and wait for the computer to power off 6.958
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.387
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.383
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.274
When the network is plugged 0.019
And Tor is ready 40.969
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.393
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.720
Given I shutdown Tails and wait for the computer to power off 4.053
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.833
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.291
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.043
# 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.166
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.031
And Tor is ready 10.310
Then the Upgrader considers the system as up-to-date 10.686
# 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.488
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.481
After features/support/hooks.rb:331 0.752
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
21.779
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.767
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
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.048
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 11.606
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.065
After features/support/hooks.rb:331 1.039
After features/support/hooks.rb:100 0.000