Project Number Date
test_Tails_ISO_devel 4183 22 Jan 2026, 16:33

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:19.376 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.300
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.081
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.746
When I start Tails from USB drive "old" with network unplugged 53.195
Then the boot device has safe access rights 2.541
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.233
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:331 3.833
After features/support/hooks.rb:100 0.008
Tags: @product
1:24.489
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 51.455
Then Tails is running from USB drive "old" 0.244
And I create a persistent partition 23.228
And I take note of which tps features are available 0.678
Then a Tails persistence partition exists on USB drive "old" 0.507
And I shutdown Tails and wait for the computer to power off 8.313
After features/support/hooks.rb:331 0.374
After features/support/hooks.rb:100 0.007
Tags: @product
1:25.748
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 59.957
Then Tails is running from USB drive "old" 0.256
And all tps features are active 1.091
When I write some files expected to persist 1.281
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.292
And all persistent directories from the old Tails version have safe access rights 1.786
And I take note of which tps features are available 0.143
And I shutdown Tails and wait for the computer to power off 8.123
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.577
After features/support/hooks.rb:331 0.623
After features/support/hooks.rb:100 0.006
Tags: @product
2:20.309
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 7.968
And I log in to a new session 14.690
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.792
And I plug USB drive "to_upgrade" 2.248
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.965
Then the running Tails is installed on USB drive "to_upgrade" 16.363
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:331 3.917
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.550
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.428
Then all tps features from the old Tails version are active 0.946
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.452
And the expected persistent files created with the old Tails version are present in the filesystem 1.397
And all persistent directories from the old Tails version have safe access rights 2.031
After features/support/hooks.rb:331 0.743
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:28.146
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.590
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.378
When the network is plugged 0.038
And Tor is ready 43.342
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.388
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.665
Given I shutdown Tails and wait for the computer to power off 14.381
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.790
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.080
And the file system changes introduced in version 6.2~testoverlayfs are present 0.212
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.202
When the network is plugged 0.018
And Tor is ready 11.572
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.645
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.298
Given I shutdown Tails and wait for the computer to power off 8.036
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.649
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.103
And the file system changes introduced in version 6.3~testoverlayfs are present 0.344
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.015
And Tor is ready 9.930
Then the Upgrader considers the system as up-to-date 10.480
# 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.304
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.355
After features/support/hooks.rb:331 0.827
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
19.830
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.844
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.431
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.163
After features/support/hooks.rb:331 0.906
After features/support/hooks.rb:100 0.000