Project Number Date
test_Tails_ISO_stable 6276 08 Apr 2026, 11:16

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:13.040 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:13.731
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 14.063
When I start Tails from USB drive "old" with network unplugged 55.272
Then the boot device has safe access rights 2.583
And Tails is running from USB drive "old" 0.217
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 1.402
After features/support/hooks.rb:100 0.021
Tags: @product
1:30.978
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login 55.545
Then Tails is running from USB drive "old" 0.273
And I create a persistent partition 25.622
And I take note of which tps features are available 0.693
Then a Tails persistence partition exists on USB drive "old" 0.613
And I shutdown Tails and wait for the computer to power off 8.168
After features/support/hooks.rb:331 0.408
After features/support/hooks.rb:100 0.008
Tags: @product
1:29.492
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.973
Then Tails is running from USB drive "old" 0.255
And all tps features are active 1.125
When I write some files expected to persist 1.274
# 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.442
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.151
And I shutdown Tails and wait for the computer to power off 8.178
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.898
After features/support/hooks.rb:331 0.351
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.512
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.407
And I log in to a new session 17.101
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.896
And I plug USB drive "to_upgrade" 2.246
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.876
Then the running Tails is installed on USB drive "to_upgrade" 16.696
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 3.977
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.447
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.113
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.273
Then all tps features from the old Tails version are active 1.067
And Tails is running from USB drive "to_upgrade" 0.232
And the boot device has safe access rights 2.569
And the expected persistent files created with the old Tails version are present in the filesystem 1.232
And all persistent directories from the old Tails version have safe access rights 1.959
After features/support/hooks.rb:331 0.822
After features/support/hooks.rb:100 0.025
4:53.679
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.666
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.361
When the network is plugged 0.013
And Tor is ready 24.146
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.371
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.786
Given I shutdown Tails and wait for the computer to power off 11.763
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.221
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.185
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.183
When the network is plugged 0.020
And Tor is ready 39.503
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.422
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.066
Given I shutdown Tails and wait for the computer to power off 17.354
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.734
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.195
And the file system changes introduced in version 6.3~testoverlayfs are present 0.415
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.017
And Tor is ready 20.957
Then the Upgrader considers the system as up-to-date 0.129
# 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.286
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.357
After features/support/hooks.rb:331 1.060
After features/support/hooks.rb:100 0.014
27.197
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.891
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
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.024
And Tor is ready 18.527
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.409
After features/support/hooks.rb:331 1.268
After features/support/hooks.rb:100 0.000