Project Number Date
test_Tails_ISO_devel 4290 23 Mar 2026, 15:31

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:31.947 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:8.583
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.112
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.533
When I start Tails from USB drive "old" with network unplugged 50.232
Then the boot device has safe access rights 3.022
And Tails is running from USB drive "old" 0.201
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:331 3.522
After features/support/hooks.rb:100 0.007
Tags: @product
1:25.431
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 54.290
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 25.466
And I take note of which tps features are available 0.745
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 4.079
After features/support/hooks.rb:331 0.478
After features/support/hooks.rb:100 0.062
Tags: @product
1:28.577
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.131
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.045
Then Tails is running from USB drive "old" 0.244
And all tps features are active 1.241
When I write some files expected to persist 1.429
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.449
And all persistent directories from the old Tails version have safe access rights 2.171
And I take note of which tps features are available 0.193
And I shutdown Tails and wait for the computer to power off 7.926
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.559
After features/support/hooks.rb:331 0.267
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.649
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.626
And I log in to a new session 14.105
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.681
And I plug USB drive "to_upgrade" 2.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.536
Then the running Tails is installed on USB drive "to_upgrade" 16.163
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.153
After features/support/hooks.rb:331 2.851
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.603
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.698
Then all tps features from the old Tails version are active 1.098
And Tails is running from USB drive "to_upgrade" 0.286
And the boot device has safe access rights 2.496
And the expected persistent files created with the old Tails version are present in the filesystem 1.054
And all persistent directories from the old Tails version have safe access rights 1.910
After features/support/hooks.rb:331 0.676
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:39.882
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.515
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
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.404
When the network is plugged 0.020
And Tor is ready 20.444
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.443
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.804
Given I shutdown Tails and wait for the computer to power off 20.545
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.606
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.212
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.234
When the network is plugged 0.017
And Tor is ready 21.029
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.388
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.280
Given I shutdown Tails and wait for the computer to power off 17.643
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.046
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.318
And the file system changes introduced in version 6.3~testoverlayfs are present 0.362
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.037
And Tor is ready 22.136
Then the Upgrader considers the system as up-to-date 0.108
# 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.310
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.422
After features/support/hooks.rb:331 0.679
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
25.219
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.618
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 16.802
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.442
After features/support/hooks.rb:331 0.975
After features/support/hooks.rb:100 0.000