Project Number Date
test_Tails_ISO_devel 4324 07 Apr 2026, 07:34

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:3.847 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.799
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 12.931
When I start Tails from USB drive "old" with network unplugged 51.370
Then the boot device has safe access rights 2.587
And Tails is running from USB drive "old" 0.213
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.229
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 3.851
After features/support/hooks.rb:100 0.025
Tags: @product
1:20.478
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 52.758
Then Tails is running from USB drive "old" 0.272
And I create a persistent partition 23.566
And I take note of which tps features are available 0.660
Then a Tails persistence partition exists on USB drive "old" 0.499
And I shutdown Tails and wait for the computer to power off 2.675
After features/support/hooks.rb:331 0.368
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.110
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.506
Then Tails is running from USB drive "old" 0.277
And all tps features are active 1.005
When I write some files expected to persist 1.208
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.408
And all persistent directories from the old Tails version have safe access rights 1.756
And I take note of which tps features are available 0.176
And I shutdown Tails and wait for the computer to power off 7.935
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.621
After features/support/hooks.rb:331 0.208
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.397
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.441
And I log in to a new session 12.280
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.784
And I plug USB drive "to_upgrade" 2.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.282
Then the running Tails is installed on USB drive "to_upgrade" 15.108
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 2.407
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.625
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.319
Then all tps features from the old Tails version are active 0.935
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.270
And the expected persistent files created with the old Tails version are present in the filesystem 1.047
And all persistent directories from the old Tails version have safe access rights 1.758
After features/support/hooks.rb:331 0.588
After features/support/hooks.rb:100 0.006
4:29.156
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.307
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.203
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.334
When the network is plugged 0.013
And Tor is ready 20.396
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.354
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.015
Given I shutdown Tails and wait for the computer to power off 19.700
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.812
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.020
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.034
# 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.208
When the network is plugged 0.020
And Tor is ready 20.232
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.358
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.766
Given I shutdown Tails and wait for the computer to power off 18.431
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.630
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.079
And the file system changes introduced in version 6.3~testoverlayfs are present 0.357
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.173
When the network is plugged 0.013
And Tor is ready 21.666
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.489
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.442
After features/support/hooks.rb:331 0.773
After features/support/hooks.rb:100 0.011
25.278
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.329
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
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.014
And Tor is ready 17.273
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.340
After features/support/hooks.rb:331 0.899
After features/support/hooks.rb:100 0.000