Project Number Date
test_Tails_ISO_devel 4274 12 Mar 2026, 15:22

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 13:35.101 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:3.026
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.885
When I start Tails from USB drive "old" with network unplugged 43.517
Then the boot device has safe access rights 2.827
And Tails is running from USB drive "old" 0.260
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 1.512
After features/support/hooks.rb:100 0.010
Tags: @product
1:30.628
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 56.048
Then Tails is running from USB drive "old" 0.275
And I create a persistent partition 25.698
And I take note of which tps features are available 0.817
Then a Tails persistence partition exists on USB drive "old" 0.574
And I shutdown Tails and wait for the computer to power off 7.139
After features/support/hooks.rb:331 0.230
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.978
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.183
Then Tails is running from USB drive "old" 0.240
And all tps features are active 1.073
When I write some files expected to persist 1.350
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.508
And all persistent directories from the old Tails version have safe access rights 1.944
And I take note of which tps features are available 0.163
And I shutdown Tails and wait for the computer to power off 8.170
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.084
After features/support/hooks.rb:331 0.418
After features/support/hooks.rb:100 0.006
Tags: @product
2:20.988
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 9.140
And I log in to a new session 13.560
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.062
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.925
Then the running Tails is installed on USB drive "to_upgrade" 17.598
And I unplug USB drive "to_upgrade" 0.351
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:331 8.041
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.567
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.664
Then all tps features from the old Tails version are active 1.753
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 3.082
And the expected persistent files created with the old Tails version are present in the filesystem 1.335
And all persistent directories from the old Tails version have safe access rights 2.421
After features/support/hooks.rb:331 0.843
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:57.496
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.741
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.023
And Tor is ready 29.269
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.439
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.117
Given I shutdown Tails and wait for the computer to power off 19.892
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.277
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.301
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# 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.208
When the network is plugged 0.016
And Tor is ready 20.876
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.386
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.024
Given I shutdown Tails and wait for the computer to power off 18.087
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.829
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.188
And the file system changes introduced in version 6.3~testoverlayfs are present 0.408
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.193
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.017
And Tor is ready 21.654
Then the Upgrader considers the system as up-to-date 0.120
# 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.908
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.454
After features/support/hooks.rb:331 0.761
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
50.415
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 7.844
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 41.771
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.393
After features/support/hooks.rb:331 0.783
After features/support/hooks.rb:100 0.000