Project Number Date
test_Tails_ISO_stop-using-boum-org-addresses-with-autoreply 1 05 May 2026, 11:44

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:23.302 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:21.429
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 14.931
When I start Tails from USB drive "old" with network unplugged 1:1.426
Then the boot device has safe access rights 3.198
And Tails is running from USB drive "old" 0.277
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.163
After features/support/hooks.rb:331 3.754
After features/support/hooks.rb:100 0.024
Tags: @product
1:38.164
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login 59.893
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 27.988
And I take note of which tps features are available 1.555
Then a Tails persistence partition exists on USB drive "old" 1.182
And I shutdown Tails and wait for the computer to power off 7.179
After features/support/hooks.rb:331 0.310
After features/support/hooks.rb:100 0.013
Tags: @product
1:33.318
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.107
Then Tails is running from USB drive "old" 0.241
And all tps features are active 1.653
When I write some files expected to persist 1.419
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.537
And all persistent directories from the old Tails version have safe access rights 2.315
And I take note of which tps features are available 0.175
And I shutdown Tails and wait for the computer to power off 4.175
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.441
After features/support/hooks.rb:331 0.529
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.142
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 8.350
And I log in to a new session 13.945
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.103
And I plug USB drive "to_upgrade" 2.334
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.307
Then the running Tails is installed on USB drive "to_upgrade" 16.818
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 3.065
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.407
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.137
Then all tps features from the old Tails version are active 1.004
And Tails is running from USB drive "to_upgrade" 0.258
And the boot device has safe access rights 2.575
And the expected persistent files created with the old Tails version are present in the filesystem 1.317
And all persistent directories from the old Tails version have safe access rights 2.046
After features/support/hooks.rb:331 0.845
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
4:51.247
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 9.206
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.360
When the network is plugged 0.014
And Tor is ready 23.789
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.417
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.235
Given I shutdown Tails and wait for the computer to power off 19.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.352
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.200
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.195
When the network is plugged 0.016
And Tor is ready 22.039
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.420
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.155
Given I shutdown Tails and wait for the computer to power off 17.886
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.294
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.837
And the file system changes introduced in version 6.3~testoverlayfs are present 0.524
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.017
And Tor is ready 22.437
Then the Upgrader considers the system as up-to-date 0.107
# 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 5.387
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.413
After features/support/hooks.rb:331 0.804
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
27.592
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.654
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 19.134
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.412
After features/support/hooks.rb:331 0.720
After features/support/hooks.rb:100 0.000