Project Number Date
test_Tails_ISO_stable 6238 26 Mar 2026, 12:51

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:36.839 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:16.726
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.598
When I start Tails from USB drive "old" with network unplugged 58.361
Then the boot device has safe access rights 2.982
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 1.662
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.126
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 54.566
Then Tails is running from USB drive "old" 0.276
And I create a persistent partition 23.912
And I take note of which tps features are available 0.771
Then a Tails persistence partition exists on USB drive "old" 0.603
And I shutdown Tails and wait for the computer to power off 7.936
After features/support/hooks.rb:331 0.283
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.763
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.479
Then Tails is running from USB drive "old" 0.351
And all tps features are active 1.263
When I write some files expected to persist 1.399
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 1.935
And I take note of which tps features are available 0.159
And I shutdown Tails and wait for the computer to power off 8.175
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.336
After features/support/hooks.rb:331 0.597
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.977
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 without a persistent partition and stopped at Tails Greeter's login screen 8.244
And I log in to a new session 12.948
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.805
And I plug USB drive "to_upgrade" 2.236
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.897
Then the running Tails is installed on USB drive "to_upgrade" 15.393
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.247
After features/support/hooks.rb:331 2.331
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.002
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.580
Then all tps features from the old Tails version are active 1.283
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 2.678
And the expected persistent files created with the old Tails version are present in the filesystem 1.169
And all persistent directories from the old Tails version have safe access rights 1.910
After features/support/hooks.rb:331 0.686
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:33.200
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 8.351
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.355
When the network is plugged 0.015
And Tor is ready 20.374
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.373
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.811
Given I shutdown Tails and wait for the computer to power off 14.810
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.464
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.327
And the file system changes introduced in version 6.2~testoverlayfs are present 0.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.191
# 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.237
When the network is plugged 0.016
And Tor is ready 21.111
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.389
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.146
Given I shutdown Tails and wait for the computer to power off 17.626
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.698
Then Tails is running version 6.3~testoverlayfs 0.032
And all tps features are active 1.520
And the file system changes introduced in version 6.3~testoverlayfs are present 0.388
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.229
When the network is plugged 0.028
And Tor is ready 20.630
Then the Upgrader considers the system as up-to-date 0.187
# 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.332
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.436
After features/support/hooks.rb:331 1.005
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
26.041
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.653
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 17.679
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.379
After features/support/hooks.rb:331 0.711
After features/support/hooks.rb:100 0.000