Project Number Date
test_Tails_ISO_stable 5691 01 Jun 2025, 12:25

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 18:38.397 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
2:3.625
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.472
When I start Tails from USB drive "old" with network unplugged 1:27.033
Then the boot device has safe access rights 2.919
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:330 11.036
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.599
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:22.243
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 31.123
And I take note of which tps features are available 1.618
Then a Tails persistence partition exists on USB drive "old" 0.761
And I shutdown Tails and wait for the computer to power off 8.298
After features/support/hooks.rb:330 0.177
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.014
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.178
Then Tails is running from USB drive "old" 0.420
And all tps features are active 1.786
When I write some files expected to persist 1.643
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.298
And all persistence configuration files have safe access rights 0.458
And all persistent directories from the old Tails version have safe access rights 2.301
And I take note of which tps features are available 0.441
And I shutdown Tails and wait for the computer to power off 6.362
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.919
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.490
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 without a persistent partition and stopped at Tails Greeter's login screen 9.832
And I log in to a new session 17.325
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.602
And I plug USB drive "to_upgrade" 2.438
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.705
Then the running Tails is installed on USB drive "to_upgrade" 26.206
And I unplug USB drive "to_upgrade" 0.186
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:330 3.565
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.250
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.157
Then all tps features from the old Tails version are active 1.506
And Tails is running from USB drive "to_upgrade" 0.296
And the boot device has safe access rights 3.393
And the expected persistent files created with the old Tails version are present in the filesystem 1.464
And all persistent directories from the old Tails version have safe access rights 2.251
After features/support/hooks.rb:330 1.247
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:17.947
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 11.572
And no SquashFS delta is installed 0.317
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.415
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.065
And Tor is ready 19.442
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.432
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.524
Given I shutdown Tails and wait for the computer to power off 8.443
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.690
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.316
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.350
When the network is plugged 0.077
And Tor is ready 19.322
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.429
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.522
Given I shutdown Tails and wait for the computer to power off 4.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.567
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.871
And the file system changes introduced in version 6.3~testoverlayfs are present 0.474
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.382
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.068
And Tor is ready 19.416
Then the Upgrader considers the system as up-to-date 10.847
# 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 15.481
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.740
After features/support/hooks.rb:330 0.753
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
35.469
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.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.446
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.121
But a current signing key is available on our website 0.000
When the network is plugged 0.107
And Tor is ready 18.143
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.496
After features/support/hooks.rb:330 1.166
After features/support/hooks.rb:100 0.000