Project Number Date
test_Tails_ISO_stable 6348 04 May 2026, 11:21

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:32.049 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:7.996
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.099
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.009
When I start Tails from USB drive "old" with network unplugged 49.150
Then the boot device has safe access rights 2.936
And Tails is running from USB drive "old" 0.257
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.223
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:331 3.612
After features/support/hooks.rb:100 0.047
Tags: @product
1:24.912
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 54.545
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 24.481
And I take note of which tps features are available 0.752
Then a Tails persistence partition exists on USB drive "old" 0.567
And I shutdown Tails and wait for the computer to power off 4.257
After features/support/hooks.rb:331 0.501
After features/support/hooks.rb:100 0.005
Tags: @product
1:27.916
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.673
Then Tails is running from USB drive "old" 0.205
And all tps features are active 1.161
When I write some files expected to persist 1.245
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 2.204
And I take note of which tps features are available 0.243
And I shutdown Tails and wait for the computer to power off 8.324
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.196
After features/support/hooks.rb:331 0.448
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.510
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.112
And I log in to a new session 13.278
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.926
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.384
Then the running Tails is installed on USB drive "to_upgrade" 16.303
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 2.166
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.358
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.632
Then all tps features from the old Tails version are active 1.122
And Tails is running from USB drive "to_upgrade" 0.231
And the boot device has safe access rights 2.746
And the expected persistent files created with the old Tails version are present in the filesystem 1.417
And all persistent directories from the old Tails version have safe access rights 2.134
After features/support/hooks.rb:331 0.853
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:39.436
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.989
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.191
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.504
When the network is plugged 0.015
And Tor is ready 20.812
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.377
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.202
Given I shutdown Tails and wait for the computer to power off 20.246
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.635
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.300
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
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.131
# 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.312
When the network is plugged 0.016
And Tor is ready 21.521
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.377
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.885
Given I shutdown Tails and wait for the computer to power off 17.542
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.801
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.151
And the file system changes introduced in version 6.3~testoverlayfs are present 0.422
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.169
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.218
When the network is plugged 0.019
And Tor is ready 20.709
Then the Upgrader considers the system as up-to-date 0.120
# 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.694
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.371
After features/support/hooks.rb:331 1.015
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
26.918
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 7.342
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
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.014
And Tor is ready 18.852
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.388
After features/support/hooks.rb:331 0.809
After features/support/hooks.rb:100 0.000