Project Number Date
test_Tails_ISO_devel 4123 15 Dec 2025, 17:51

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 14:17.094 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:36.758
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.164
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 29.016
When I start Tails from USB drive "old" with network unplugged 1:2.328
Then the boot device has safe access rights 3.339
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.217
And I unplug USB drive "old" 0.163
After features/support/hooks.rb:331 3.499
After features/support/hooks.rb:100 0.009
Tags: @product
1:55.519
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:10.127
Then Tails is running from USB drive "old" 0.287
And I create a persistent partition 29.821
And I take note of which tps features are available 6.585
Then a Tails persistence partition exists on USB drive "old" 0.693
And I shutdown Tails and wait for the computer to power off 7.800
After features/support/hooks.rb:331 0.594
After features/support/hooks.rb:100 0.010
Tags: @product
2:3.665
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:29.066
Then Tails is running from USB drive "old" 0.697
And all tps features are active 1.811
When I write some files expected to persist 1.542
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.345
And all persistent directories from the old Tails version have safe access rights 2.321
And I take note of which tps features are available 0.457
And I shutdown Tails and wait for the computer to power off 8.009
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.018
After features/support/hooks.rb:331 0.298
After features/support/hooks.rb:100 0.011
Tags: @product
2:18.944
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.154
And I log in to a new session 10.214
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.204
And I plug USB drive "to_upgrade" 2.532
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.642
Then the running Tails is installed on USB drive "to_upgrade" 19.736
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.258
After features/support/hooks.rb:331 3.969
After features/support/hooks.rb:100 0.000
Tags: @product
1:28.312
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:17.229
Then all tps features from the old Tails version are active 2.012
And Tails is running from USB drive "to_upgrade" 0.389
And the boot device has safe access rights 4.038
And the expected persistent files created with the old Tails version are present in the filesystem 1.760
And all persistent directories from the old Tails version have safe access rights 2.693
After features/support/hooks.rb:331 0.627
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
4:31.130
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.011
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.557
When the network is plugged 0.059
And Tor is ready 12.880
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.162
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.076
Given I shutdown Tails and wait for the computer to power off 9.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.287
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.579
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.241
# 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.377
When the network is plugged 0.054
And Tor is ready 11.647
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.892
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.308
Given I shutdown Tails and wait for the computer to power off 7.810
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.415
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.415
And the file system changes introduced in version 6.3~testoverlayfs are present 0.460
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.052
And Tor is ready 13.101
Then the Upgrader considers the system as up-to-date 10.745
# 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 6.289
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.592
After features/support/hooks.rb:331 1.229
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
22.763
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.187
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 10.199
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.912
After features/support/hooks.rb:331 1.355
After features/support/hooks.rb:100 0.000