Project Number Date
test_Tails_ISO_stable 5634 08 May 2025, 08:55

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:59.585 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:1.894
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 29.452
When I start Tails from USB drive "old" with network unplugged 1:27.222
Then the boot device has safe access rights 2.957
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:330 1.190
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.586
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:22.211
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 30.316
And I take note of which tps features are available 1.568
Then a Tails persistence partition exists on USB drive "old" 0.826
And I shutdown Tails and wait for the computer to power off 8.150
After features/support/hooks.rb:330 0.186
After features/support/hooks.rb:100 0.007
Tags: @product
2:51.134
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.115
Then Tails is running from USB drive "old" 0.391
And all tps features are active 2.264
When I write some files expected to persist 1.725
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.363
And all persistent directories from the old Tails version have safe access rights 2.298
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 4.357
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.741
After features/support/hooks.rb:330 0.137
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.752
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 10.000
And I log in to a new session 19.877
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.478
And I plug USB drive "to_upgrade" 2.480
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.426
Then the running Tails is installed on USB drive "to_upgrade" 23.063
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 1.823
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.414
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.981
Then all tps features from the old Tails version are active 1.603
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.473
And the expected persistent files created with the old Tails version are present in the filesystem 1.342
And all persistent directories from the old Tails version have safe access rights 2.450
After features/support/hooks.rb:330 0.871
After features/support/hooks.rb:100 0.009
6:38.389
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.794
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.385
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.371
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.495
When the network is plugged 0.078
And Tor is ready 22.965
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.291
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.055
Given I shutdown Tails and wait for the computer to power off 10.632
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.629
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 2.342
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.318
# 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.075
And Tor is ready 17.708
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.877
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.622
Given I shutdown Tails and wait for the computer to power off 8.581
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.928
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.239
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.076
And Tor is ready 16.307
Then the Upgrader considers the system as up-to-date 0.294
# 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.220
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.019
After features/support/hooks.rb:330 0.682
After features/support/hooks.rb:100 0.019
36.413
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 9.968
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 19.345
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.580
After features/support/hooks.rb:330 1.017
After features/support/hooks.rb:100 0.000