Project Number Date
test_Tails_ISO_stable 6148 15 Feb 2026, 11:55

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:21.657 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:54.386
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.065
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.376
When I start Tails from USB drive "old" with network unplugged 1:35.192
Then the boot device has safe access rights 3.027
And Tails is running from USB drive "old" 0.242
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 1.669
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.892
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 55.776
Then Tails is running from USB drive "old" 0.295
And I create a persistent partition 24.322
And I take note of which tps features are available 0.724
Then a Tails persistence partition exists on USB drive "old" 0.573
And I shutdown Tails and wait for the computer to power off 8.142
After features/support/hooks.rb:331 0.500
After features/support/hooks.rb:100 0.006
Tags: @product
1:27.110
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.726
Then Tails is running from USB drive "old" 0.248
And all tps features are active 1.221
When I write some files expected to persist 1.343
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.361
And all persistent directories from the old Tails version have safe access rights 1.928
And I take note of which tps features are available 0.159
And I shutdown Tails and wait for the computer to power off 7.999
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.909
After features/support/hooks.rb:331 0.181
After features/support/hooks.rb:100 0.006
Tags: @product
2:21.212
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 without a persistent partition and stopped at Tails Greeter's login screen 8.659
And I log in to a new session 12.839
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.794
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.915
Then the running Tails is installed on USB drive "to_upgrade" 18.490
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 0.727
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.024
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.175
Then all tps features from the old Tails version are active 1.286
And Tails is running from USB drive "to_upgrade" 0.270
And the boot device has safe access rights 2.745
And the expected persistent files created with the old Tails version are present in the filesystem 1.354
And all persistent directories from the old Tails version have safe access rights 2.131
After features/support/hooks.rb:331 0.795
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
3:33.916
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.235
And no SquashFS delta is installed 0.170
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.224
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.025
And Tor is ready 13.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.366
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.938
Given I shutdown Tails and wait for the computer to power off 11.580
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.807
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.110
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.247
When the network is plugged 0.018
And Tor is ready 12.076
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.687
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.213
Given I shutdown Tails and wait for the computer to power off 4.017
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.831
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.176
And the file system changes introduced in version 6.3~testoverlayfs are present 0.358
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.018
And Tor is ready 11.224
Then the Upgrader considers the system as up-to-date 0.113
# 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.989
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.545
After features/support/hooks.rb:331 1.046
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
21.114
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.583
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
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.293
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.909
After features/support/hooks.rb:331 0.814
After features/support/hooks.rb:100 0.000