Project Number Date
test_Tails_ISO_devel 4292 25 Mar 2026, 11:24

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:7.850 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:6.705
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.097
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 14.574
When I start Tails from USB drive "old" with network unplugged 47.532
Then the boot device has safe access rights 2.798
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.179
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:331 1.179
After features/support/hooks.rb:100 0.006
Tags: @product
1:30.076
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 56.243
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 24.031
And I take note of which tps features are available 0.770
Then a Tails persistence partition exists on USB drive "old" 0.582
And I shutdown Tails and wait for the computer to power off 8.135
After features/support/hooks.rb:331 0.270
After features/support/hooks.rb:100 0.007
Tags: @product
1:25.653
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.570
Then Tails is running from USB drive "old" 0.268
And all tps features are active 1.204
When I write some files expected to persist 1.264
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.471
And all persistent directories from the old Tails version have safe access rights 1.969
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.282
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.197
After features/support/hooks.rb:331 0.191
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.780
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.596
And I log in to a new session 18.938
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.916
And I plug USB drive "to_upgrade" 2.276
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.296
Then the running Tails is installed on USB drive "to_upgrade" 16.449
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:331 3.909
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.057
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.026
Then all tps features from the old Tails version are active 1.016
And Tails is running from USB drive "to_upgrade" 0.259
And the boot device has safe access rights 2.805
And the expected persistent files created with the old Tails version are present in the filesystem 1.047
And all persistent directories from the old Tails version have safe access rights 1.816
After features/support/hooks.rb:331 0.689
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:57.334
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.449
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.331
When the network is plugged 0.017
And Tor is ready 33.305
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.403
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.195
Given I shutdown Tails and wait for the computer to power off 21.567
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.423
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.194
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
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.170
# 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.013
And Tor is ready 20.340
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.428
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.224
Given I shutdown Tails and wait for the computer to power off 17.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.840
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.206
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.016
And Tor is ready 20.795
Then the Upgrader considers the system as up-to-date 0.117
# 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.422
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.422
After features/support/hooks.rb:331 0.857
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
29.243
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.570
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 20.735
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.425
After features/support/hooks.rb:331 0.661
After features/support/hooks.rb:100 0.000