Project Number Date
test_Tails_ISO_stable 6044 08 Jan 2026, 18: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 11:25.339 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:4.308
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.064
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.388
When I start Tails from USB drive "old" with network unplugged 46.152
Then the boot device has safe access rights 2.890
And Tails is running from USB drive "old" 0.254
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.149
After features/support/hooks.rb:331 3.835
After features/support/hooks.rb:100 0.016
Tags: @product
1:26.295
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 52.877
Then Tails is running from USB drive "old" 0.304
And I create a persistent partition 23.870
And I take note of which tps features are available 0.666
Then a Tails persistence partition exists on USB drive "old" 0.580
And I shutdown Tails and wait for the computer to power off 7.928
After features/support/hooks.rb:331 0.581
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.411
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.811
Then Tails is running from USB drive "old" 0.381
And all tps features are active 1.376
When I write some files expected to persist 1.360
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.381
And all persistent directories from the old Tails version have safe access rights 1.893
And I take note of which tps features are available 0.185
And I shutdown Tails and wait for the computer to power off 7.977
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.789
After features/support/hooks.rb:331 0.423
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.639
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.379
And I log in to a new session 13.191
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.799
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.061
Then the running Tails is installed on USB drive "to_upgrade" 15.655
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.162
After features/support/hooks.rb:331 0.813
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.346
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.696
Then all tps features from the old Tails version are active 1.205
And Tails is running from USB drive "to_upgrade" 0.298
And the boot device has safe access rights 2.712
And the expected persistent files created with the old Tails version are present in the filesystem 1.326
And all persistent directories from the old Tails version have safe access rights 2.037
After features/support/hooks.rb:331 0.918
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
3:41.578
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.188
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.018
And Tor is ready 12.849
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.148
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.284
Given I shutdown Tails and wait for the computer to power off 9.633
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.145
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.212
And the file system changes introduced in version 6.2~testoverlayfs are present 0.235
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.139
# 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.249
When the network is plugged 0.014
And Tor is ready 10.989
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.391
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.424
Given I shutdown Tails and wait for the computer to power off 8.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.205
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.242
And the file system changes introduced in version 6.3~testoverlayfs are present 0.395
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.204
When the network is plugged 0.015
And Tor is ready 10.201
Then the Upgrader considers the system as up-to-date 10.673
# 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.464
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.431
After features/support/hooks.rb:331 0.891
After features/support/hooks.rb:100 0.043
Tags: @product @automatic_upgrade
21.758
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.253
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.457
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.631
After features/support/hooks.rb:331 0.995
After features/support/hooks.rb:100 0.000