Project Number Date
test_Tails_ISO_stable 5408 21 Jan 2025, 18:12

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 21:15.681 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:44.307
Before features/support/hooks.rb:269 0.005
Given a computer 0.275
And I create a 7200 MiB disk named "old" 0.072
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 54.387
When I start Tails from USB drive "old" with network unplugged 1:44.154
Then the boot device has safe access rights 3.182
And Tails is running from USB drive "old" 0.429
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 0.224
After features/support/hooks.rb:326 3.822
After features/support/hooks.rb:100 0.012
Tags: @product
2:21.871
Before features/support/hooks.rb:269 0.004
Given a computer 1.842
And I start Tails from USB drive "old" with network unplugged and I login 1:27.842
Then Tails is running from USB drive "old" 0.394
And I create a persistent partition 34.336
And I take note of which tps features are available 7.060
Then a Tails persistence partition exists on USB drive "old" 1.409
And I shutdown Tails and wait for the computer to power off 8.985
After features/support/hooks.rb:326 0.216
After features/support/hooks.rb:100 0.011
Tags: @product
3:10.958
Before features/support/hooks.rb:269 0.007
Given a computer 1.343
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.189
Then Tails is running from USB drive "old" 1.448
And all tps features are active 2.622
When I write some files expected to persist 2.083
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.278
And all persistence configuration files have safe access rights 0.460
And all persistent directories from the old Tails version have safe access rights 2.725
And I take note of which tps features are available 0.547
And I shutdown Tails and wait for the computer to power off 4.376
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.883
After features/support/hooks.rb:326 0.103
After features/support/hooks.rb:100 0.007
Tags: @product
2:32.411
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.781
And I log in to a new session 18.417
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.931
And I plug USB drive "to_upgrade" 2.548
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.990
Then the running Tails is installed on USB drive "to_upgrade" 24.314
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 4.633
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.443
Before features/support/hooks.rb:269 0.005
Given a computer 0.253
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.932
Then all tps features from the old Tails version are active 2.415
And Tails is running from USB drive "to_upgrade" 0.617
And the boot device has safe access rights 4.359
And the expected persistent files created with the old Tails version are present in the filesystem 2.257
And all persistent directories from the old Tails version have safe access rights 3.607
After features/support/hooks.rb:326 0.906
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
7:18.955
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 29.158
And no SquashFS delta is installed 0.134
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.589
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.419
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.674
When the network is plugged 0.133
And Tor is ready 24.373
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.408
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.529
Given I shutdown Tails and wait for the computer to power off 11.451
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.634
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.954
And the file system changes introduced in version 6.2~testoverlayfs are present 0.342
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.344
When the network is plugged 0.082
And Tor is ready 15.741
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.983
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.567
Given I shutdown Tails and wait for the computer to power off 4.385
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.626
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.861
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.350
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.458
When the network is plugged 0.108
And Tor is ready 21.184
Then the Upgrader considers the system as up-to-date 0.365
# 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.894
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.063
After features/support/hooks.rb:326 0.862
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
40.732
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.836
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.396
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the signing key used by the Upgrader is outdated 0.102
But a current signing key is available on our website 0.000
When the network is plugged 0.092
And Tor is ready 18.480
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.721
After features/support/hooks.rb:326 1.187
After features/support/hooks.rb:100 0.000