Project Number Date
test_Tails_ISO_stable 6212 17 Mar 2026, 13:01

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:43.264 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:37.607
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.123
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.668
When I start Tails from USB drive "old" with network unplugged 1:17.409
Then the boot device has safe access rights 3.504
And Tails is running from USB drive "old" 0.292
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:331 1.515
After features/support/hooks.rb:100 0.026
Tags: @product
1:36.117
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.140
And I start Tails from USB drive "old" with network unplugged and I login 1:0.526
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 25.252
And I take note of which tps features are available 0.914
Then a Tails persistence partition exists on USB drive "old" 0.624
And I shutdown Tails and wait for the computer to power off 8.305
After features/support/hooks.rb:331 0.312
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.213
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:5.776
Then Tails is running from USB drive "old" 0.343
And all tps features are active 1.478
When I write some files expected to persist 1.615
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.529
And all persistent directories from the old Tails version have safe access rights 2.211
And I take note of which tps features are available 0.239
And I shutdown Tails and wait for the computer to power off 4.075
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.691
After features/support/hooks.rb:331 0.141
After features/support/hooks.rb:100 0.008
Tags: @product
2:21.224
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.260
And I log in to a new session 14.474
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.845
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.972
Then the running Tails is installed on USB drive "to_upgrade" 18.101
And I unplug USB drive "to_upgrade" 0.180
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 3.374
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.864
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.153
Then all tps features from the old Tails version are active 1.524
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 2.989
And the expected persistent files created with the old Tails version are present in the filesystem 1.268
And all persistent directories from the old Tails version have safe access rights 2.542
After features/support/hooks.rb:331 0.989
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
4:53.252
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.185
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.350
When the network is plugged 0.018
And Tor is ready 21.833
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.540
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.298
Given I shutdown Tails and wait for the computer to power off 21.139
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.700
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.288
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.167
# 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.031
And Tor is ready 20.495
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.434
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.482
Given I shutdown Tails and wait for the computer to power off 18.457
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.576
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.187
And the file system changes introduced in version 6.3~testoverlayfs are present 0.329
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.208
When the network is plugged 0.014
And Tor is ready 22.757
Then the Upgrader considers the system as up-to-date 0.198
# 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 5.330
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.662
After features/support/hooks.rb:331 0.863
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
27.984
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.953
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 19.327
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.376
After features/support/hooks.rb:331 0.789
After features/support/hooks.rb:100 0.000