Project Number Date
test_Tails_ISO_stable 6215 18 Mar 2026, 11:03

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:41.948 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:17.175
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.715
When I start Tails from USB drive "old" with network unplugged 58.781
Then the boot device has safe access rights 2.741
And Tails is running from USB drive "old" 0.286
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:331 3.489
After features/support/hooks.rb:100 0.025
Tags: @product
1:27.488
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 54.172
Then Tails is running from USB drive "old" 0.251
And I create a persistent partition 24.875
And I take note of which tps features are available 0.673
Then a Tails persistence partition exists on USB drive "old" 0.526
And I shutdown Tails and wait for the computer to power off 6.934
After features/support/hooks.rb:331 0.371
After features/support/hooks.rb:100 0.008
Tags: @product
1:28.065
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 1:1.739
Then Tails is running from USB drive "old" 0.269
And all tps features are active 1.097
When I write some files expected to persist 1.453
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.442
And all persistent directories from the old Tails version have safe access rights 1.940
And I take note of which tps features are available 0.153
And I shutdown Tails and wait for the computer to power off 8.487
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.219
After features/support/hooks.rb:331 0.226
After features/support/hooks.rb:100 0.006
Tags: @product
2:12.715
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 without a persistent partition and stopped at Tails Greeter's login screen 8.974
And I log in to a new session 11.044
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.081
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.755
Then the running Tails is installed on USB drive "to_upgrade" 16.312
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.172
After features/support/hooks.rb:331 2.572
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.761
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.515
Then all tps features from the old Tails version are active 1.082
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 2.689
And the expected persistent files created with the old Tails version are present in the filesystem 1.058
And all persistent directories from the old Tails version have safe access rights 2.039
After features/support/hooks.rb:331 0.987
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:38.223
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.305
And no SquashFS delta is installed 0.074
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.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.014
And Tor is ready 20.018
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.376
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.281
Given I shutdown Tails and wait for the computer to power off 20.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.013
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.155
And the file system changes introduced in version 6.2~testoverlayfs are present 0.265
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.168
# 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.310
When the network is plugged 0.020
And Tor is ready 21.318
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.418
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.710
Given I shutdown Tails and wait for the computer to power off 17.269
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.556
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.275
And the file system changes introduced in version 6.3~testoverlayfs are present 0.408
And only the 6.3~testoverlayfs SquashFS delta is installed 0.103
# 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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.235
When the network is plugged 0.020
And Tor is ready 21.039
Then the Upgrader considers the system as up-to-date 0.101
# 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.766
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.467
After features/support/hooks.rb:331 0.794
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
26.519
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.042
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 17.709
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.403
After features/support/hooks.rb:331 0.701
After features/support/hooks.rb:100 0.000