Project Number Date
test_Tails_ISO_devel 3610 12 Dec 2024, 12:52

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 19:10.440 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.232
Before features/support/hooks.rb:269 0.004
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.334
When I start Tails from USB drive "old" with network unplugged 1:25.660
Then the boot device has safe access rights 2.968
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:326 6.929
After features/support/hooks.rb:100 0.010
Tags: @product
2:7.776
Before features/support/hooks.rb:269 0.004
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:25.765
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 31.172
And I take note of which tps features are available 1.417
Then a Tails persistence partition exists on USB drive "old" 0.764
And I shutdown Tails and wait for the computer to power off 8.157
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.325
Before features/support/hooks.rb:269 0.005
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.294
Then Tails is running from USB drive "old" 0.370
And all tps features are active 2.026
When I write some files expected to persist 1.820
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.289
And all persistence configuration files have safe access rights 0.466
And all persistent directories from the old Tails version have safe access rights 2.358
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.586
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.438
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.781
Before features/support/hooks.rb:269 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 11.435
And I log in to a new session 18.896
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.633
And I plug USB drive "to_upgrade" 2.404
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.330
Then the running Tails is installed on USB drive "to_upgrade" 21.649
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 7.087
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.213
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.043
Then all tps features from the old Tails version are active 1.612
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.377
And the expected persistent files created with the old Tails version are present in the filesystem 1.353
And all persistent directories from the old Tails version have safe access rights 2.291
After features/support/hooks.rb:326 0.645
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:37.373
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.754
And no SquashFS delta is installed 0.162
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.078
And Tor is ready 23.875
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.527
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.727
Given I shutdown Tails and wait for the computer to power off 13.224
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.389
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.211
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.264
When the network is plugged 0.069
And Tor is ready 18.842
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.377
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.555
Given I shutdown Tails and wait for the computer to power off 6.418
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.894
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 1.931
And the file system changes introduced in version 6.3~testoverlayfs are present 0.508
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.183
And Tor is ready 16.219
Then the Upgrader considers the system as up-to-date 0.321
# 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.358
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.937
After features/support/hooks.rb:326 0.664
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
40.738
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.468
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.906
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 21.466
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.419
After features/support/hooks.rb:326 0.689
After features/support/hooks.rb:100 0.000