Project Number Date
test_Tails_ISO_devel 3385 13 May 2024, 17:28

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 20:2.874 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:6.662
Before features/support/hooks.rb:259 0.006
Given a computer 0.159
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 32.363
When I start Tails from USB drive "old" with network unplugged 1:28.957
Then the boot device has safe access rights 3.027
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.353
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:305 3.583
After features/support/hooks.rb:89 0.008
Tags: @product
2:4.379
Before features/support/hooks.rb:259 0.004
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login 1:19.792
Then Tails is running from USB drive "old" 0.403
And I create a persistent partition 35.274
And I take note of which tps features are available 1.377
Then a Tails persistence partition exists on USB drive "old" 0.838
And I shutdown Tails and wait for the computer to power off 6.531
After features/support/hooks.rb:305 0.146
After features/support/hooks.rb:89 0.010
Tags: @product
2:58.664
Before features/support/hooks.rb:259 0.007
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.089
Then Tails is running from USB drive "old" 0.347
And all tps features are active 1.941
When I write some files expected to persist 2.217
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.437
And all persistent directories from the old Tails version have safe access rights 2.292
And I take note of which tps features are available 0.435
And I shutdown Tails and wait for the computer to power off 4.469
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.002
After features/support/hooks.rb:305 0.176
After features/support/hooks.rb:89 0.008
Tags: @product
2:25.769
Before features/support/hooks.rb:259 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 11.337
And I log in to a new session 17.376
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.039
And I plug USB drive "to_upgrade" 2.417
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.390
Then the running Tails is installed on USB drive "to_upgrade" 17.827
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:305 2.026
After features/support/hooks.rb:89 0.000
Tags: @product
2:12.879
Before features/support/hooks.rb:259 0.008
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.657
Then all tps features from the old Tails version are active 1.646
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.356
And the expected persistent files created with the old Tails version are present in the filesystem 1.370
And all persistent directories from the old Tails version have safe access rights 2.344
After features/support/hooks.rb:305 0.704
After features/support/hooks.rb:89 0.008
Tags: @product @automatic_upgrade
7:41.212
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.101
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.481
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.510
When the network is plugged 0.044
And Tor is ready 17.471
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.577
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.595
Given I shutdown Tails and wait for the computer to power off 1:19.941
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.291
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.087
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.260
When the network is plugged 0.049
And Tor is ready 19.549
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.090
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.965
Given I shutdown Tails and wait for the computer to power off 4.417
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.159
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.126
And the file system changes introduced in version 6.3~testoverlayfs are present 0.479
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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.065
And Tor is ready 16.625
Then the Upgrader considers the system as up-to-date 10.835
# 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 14.695
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.951
After features/support/hooks.rb:305 0.760
After features/support/hooks.rb:89 0.037
Tags: @product @automatic_upgrade
33.306
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.553
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.606
But a current signing key is available on our website 0.000
When the network is plugged 0.185
And Tor is ready 16.067
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.488
After features/support/hooks.rb:305 1.118
After features/support/hooks.rb:89 0.000