Project Number Date
test_Tails_ISO_stable 6338 30 Apr 2026, 11:23

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:44.538 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:11.643
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.403
When I start Tails from USB drive "old" with network unplugged 53.950
Then the boot device has safe access rights 2.568
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:331 1.246
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.620
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 55.993
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 25.623
And I take note of which tps features are available 0.773
Then a Tails persistence partition exists on USB drive "old" 0.570
And I shutdown Tails and wait for the computer to power off 8.329
After features/support/hooks.rb:331 0.313
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.336
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.960
Then Tails is running from USB drive "old" 0.250
And all tps features are active 1.151
When I write some files expected to persist 1.183
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.414
And all persistent directories from the old Tails version have safe access rights 1.930
And I take note of which tps features are available 0.141
And I shutdown Tails and wait for the computer to power off 8.054
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.015
After features/support/hooks.rb:331 0.600
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.517
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 without a persistent partition and stopped at Tails Greeter's login screen 7.957
And I log in to a new session 12.159
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.762
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.021
Then the running Tails is installed on USB drive "to_upgrade" 16.052
And I unplug USB drive "to_upgrade" 0.160
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:331 2.075
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.151
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.446
Then all tps features from the old Tails version are active 1.095
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.670
And the expected persistent files created with the old Tails version are present in the filesystem 1.391
And all persistent directories from the old Tails version have safe access rights 2.231
After features/support/hooks.rb:331 0.677
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:41.174
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.665
And no SquashFS delta is installed 0.067
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.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.216
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.337
When the network is plugged 0.019
And Tor is ready 21.119
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.389
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.718
Given I shutdown Tails and wait for the computer to power off 18.851
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.023
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.194
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.211
When the network is plugged 0.020
And Tor is ready 21.909
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.387
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.519
Given I shutdown Tails and wait for the computer to power off 17.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.327
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.151
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.042
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.018
And Tor is ready 21.657
Then the Upgrader considers the system as up-to-date 0.133
# 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.879
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.540
After features/support/hooks.rb:331 0.823
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
26.093
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.410
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 18.005
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.362
After features/support/hooks.rb:331 0.902
After features/support/hooks.rb:100 0.000