Project Number Date
test_Tails_ISO_devel 4203 01 Feb 2026, 12:08

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:8.608 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:16.678
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.274
When I start Tails from USB drive "old" with network unplugged 57.467
Then the boot device has safe access rights 3.029
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.228
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:331 3.451
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.281
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 53.964
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 24.613
And I take note of which tps features are available 0.707
Then a Tails persistence partition exists on USB drive "old" 0.535
And I shutdown Tails and wait for the computer to power off 8.096
After features/support/hooks.rb:331 0.641
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.063
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.893
Then Tails is running from USB drive "old" 0.249
And all tps features are active 1.124
When I write some files expected to persist 1.262
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.484
And all persistent directories from the old Tails version have safe access rights 2.310
And I take note of which tps features are available 0.256
And I shutdown Tails and wait for the computer to power off 8.522
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.689
After features/support/hooks.rb:331 0.339
After features/support/hooks.rb:100 0.021
Tags: @product
2:16.925
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.267
And I log in to a new session 12.502
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.954
And I plug USB drive "to_upgrade" 2.291
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.789
Then the running Tails is installed on USB drive "to_upgrade" 15.847
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:331 3.790
After features/support/hooks.rb:100 0.000
Tags: @product
1:22.156
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:14.550
Then all tps features from the old Tails version are active 1.319
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 2.816
And the expected persistent files created with the old Tails version are present in the filesystem 1.131
And all persistent directories from the old Tails version have safe access rights 2.037
After features/support/hooks.rb:331 0.645
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
3:54.777
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.306
And no SquashFS delta is installed 0.157
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.363
When the network is plugged 0.019
And Tor is ready 12.514
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.403
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.669
Given I shutdown Tails and wait for the computer to power off 12.959
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.377
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 1.244
And the file system changes introduced in version 6.2~testoverlayfs are present 0.233
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.254
When the network is plugged 0.016
And Tor is ready 10.709
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.368
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.403
Given I shutdown Tails and wait for the computer to power off 7.193
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.218
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.220
And the file system changes introduced in version 6.3~testoverlayfs are present 0.465
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.182
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.026
And Tor is ready 10.893
Then the Upgrader considers the system as up-to-date 10.565
# 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.400
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.459
After features/support/hooks.rb:331 0.746
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
21.725
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.586
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 11.052
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.759
After features/support/hooks.rb:331 1.074
After features/support/hooks.rb:100 0.000