Project Number Date
test_Tails_ISO_stable 6105 29 Jan 2026, 16:22

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 11:40.090 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:3.143
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.067
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.041
When I start Tails from USB drive "old" with network unplugged 44.556
Then the boot device has safe access rights 2.747
And Tails is running from USB drive "old" 0.247
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:331 3.466
After features/support/hooks.rb:100 0.006
Tags: @product
1:27.089
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 52.512
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 24.825
And I take note of which tps features are available 0.728
Then a Tails persistence partition exists on USB drive "old" 0.576
And I shutdown Tails and wait for the computer to power off 8.128
After features/support/hooks.rb:331 0.249
After features/support/hooks.rb:100 0.007
Tags: @product
1:22.809
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.961
Then Tails is running from USB drive "old" 0.257
And all tps features are active 0.990
When I write some files expected to persist 1.196
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.263
And all persistent directories from the old Tails version have safe access rights 1.794
And I take note of which tps features are available 0.134
And I shutdown Tails and wait for the computer to power off 7.897
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.081
After features/support/hooks.rb:331 0.551
After features/support/hooks.rb:100 0.005
Tags: @product
2:15.346
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.112
And I log in to a new session 11.666
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.717
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.246
Then the running Tails is installed on USB drive "to_upgrade" 16.126
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:331 8.935
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.396
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.132
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.688
Then all tps features from the old Tails version are active 0.984
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 2.396
And the expected persistent files created with the old Tails version are present in the filesystem 1.087
And all persistent directories from the old Tails version have safe access rights 1.879
After features/support/hooks.rb:331 0.893
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:59.823
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 8.045
And no SquashFS delta is installed 0.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.369
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.388
When the network is plugged 0.028
And Tor is ready 17.522
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.181
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.612
Given I shutdown Tails and wait for the computer to power off 22.084
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.798
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.046
And the file system changes introduced in version 6.2~testoverlayfs are present 0.199
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.169
# 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.191
When the network is plugged 0.015
And Tor is ready 10.618
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.610
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.988
Given I shutdown Tails and wait for the computer to power off 7.867
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.055
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.061
And the file system changes introduced in version 6.3~testoverlayfs are present 0.371
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.112
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.018
And Tor is ready 11.041
Then the Upgrader considers the system as up-to-date 10.498
# 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 3.684
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:331 0.539
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
21.481
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.711
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.540
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.885
After features/support/hooks.rb:331 0.687
After features/support/hooks.rb:100 0.000