Project Number Date
test_Tails_ISO_devel 4256 26 Feb 2026, 17:12

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:6.716 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.096
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.948
When I start Tails from USB drive "old" with network unplugged 52.308
Then the boot device has safe access rights 3.032
And Tails is running from USB drive "old" 0.267
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 3.486
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.455
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.124
And I start Tails from USB drive "old" with network unplugged and I login 55.524
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 26.472
And I take note of which tps features are available 0.779
Then a Tails persistence partition exists on USB drive "old" 1.158
And I shutdown Tails and wait for the computer to power off 7.146
After features/support/hooks.rb:331 0.485
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.854
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.568
Then Tails is running from USB drive "old" 0.261
And all tps features are active 1.273
When I write some files expected to persist 1.493
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.556
And all persistent directories from the old Tails version have safe access rights 2.419
And I take note of which tps features are available 0.238
And I shutdown Tails and wait for the computer to power off 4.410
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.380
After features/support/hooks.rb:331 0.498
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.690
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 without a persistent partition and stopped at Tails Greeter's login screen 9.103
And I log in to a new session 11.320
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.241
And I plug USB drive "to_upgrade" 2.252
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.490
Then the running Tails is installed on USB drive "to_upgrade" 17.011
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 0.635
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.914
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:9.372
Then all tps features from the old Tails version are active 1.149
And Tails is running from USB drive "to_upgrade" 0.419
And the boot device has safe access rights 3.270
And the expected persistent files created with the old Tails version are present in the filesystem 1.439
And all persistent directories from the old Tails version have safe access rights 2.196
After features/support/hooks.rb:331 0.835
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
4:52.969
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.286
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
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.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.495
When the network is plugged 0.016
And Tor is ready 20.797
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.583
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.773
Given I shutdown Tails and wait for the computer to power off 20.708
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.201
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.186
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.186
When the network is plugged 0.019
And Tor is ready 21.954
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.382
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.033
Given I shutdown Tails and wait for the computer to power off 18.542
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.316
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.270
And the file system changes introduced in version 6.3~testoverlayfs are present 0.357
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.233
When the network is plugged 0.018
And Tor is ready 21.880
Then the Upgrader considers the system as up-to-date 0.094
# 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.888
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.430
After features/support/hooks.rb:331 1.102
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
28.735
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 with a persistent partition enabled and logged in 8.125
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.047
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.019
And Tor is ready 19.900
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.386
After features/support/hooks.rb:331 1.100
After features/support/hooks.rb:100 0.000