Project Number Date
test_Tails_ISO_devel 4387 10 May 2026, 10:55

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:53.334 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:9.079
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 12.826
When I start Tails from USB drive "old" with network unplugged 52.282
Then the boot device has safe access rights 2.311
And Tails is running from USB drive "old" 0.201
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:331 3.488
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.876
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 51.310
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 22.945
And I take note of which tps features are available 0.653
Then a Tails persistence partition exists on USB drive "old" 0.478
And I shutdown Tails and wait for the computer to power off 8.194
After features/support/hooks.rb:331 0.466
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.254
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.930
Then Tails is running from USB drive "old" 0.305
And all tps features are active 1.100
When I write some files expected to persist 1.284
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 1.890
And I take note of which tps features are available 0.142
And I shutdown Tails and wait for the computer to power off 8.053
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.865
After features/support/hooks.rb:331 0.601
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.908
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 7.663
And I log in to a new session 12.355
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.611
And I plug USB drive "to_upgrade" 2.204
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.201
Then the running Tails is installed on USB drive "to_upgrade" 15.614
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:331 2.481
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.415
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.571
Then all tps features from the old Tails version are active 1.052
And Tails is running from USB drive "to_upgrade" 0.233
And the boot device has safe access rights 2.586
And the expected persistent files created with the old Tails version are present in the filesystem 1.065
And all persistent directories from the old Tails version have safe access rights 1.828
After features/support/hooks.rb:331 0.880
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:14.138
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.995
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.334
When the network is plugged 0.016
And Tor is ready 18.667
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.481
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.272
Given I shutdown Tails and wait for the computer to power off 5.559
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.768
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.017
And the file system changes introduced in version 6.2~testoverlayfs are present 0.253
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.188
When the network is plugged 0.013
And Tor is ready 21.645
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.396
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.995
Given I shutdown Tails and wait for the computer to power off 17.046
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.576
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.062
And the file system changes introduced in version 6.3~testoverlayfs are present 0.403
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.017
And Tor is ready 20.671
Then the Upgrader considers the system as up-to-date 0.112
# 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.122
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.408
After features/support/hooks.rb:331 0.815
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
24.661
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.284
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
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.015
And Tor is ready 16.608
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.467
After features/support/hooks.rb:331 0.828
After features/support/hooks.rb:100 0.000