Project Number Date
test_Tails_ISO_devel 3216 29 Dec 2023, 12:15

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 17:28.927 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
1:29.555
Before features/support/hooks.rb:245 0.004
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 19.691
When I start Tails from USB drive "old" with network unplugged 1:4.392
Then the boot device has safe access rights 3.221
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.275
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:291 3.509
After features/support/hooks.rb:75 0.054
Tags: @product
1:59.736
Before features/support/hooks.rb:245 0.008
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login 1:4.070
Then Tails is running from USB drive "old" 0.458
And I create a persistent partition 43.188
And I take note of which tps features are available 2.826
Then a Tails persistence partition exists on USB drive "old" 0.893
And I shutdown Tails and wait for the computer to power off 8.078
After features/support/hooks.rb:291 0.173
After features/support/hooks.rb:75 0.013
Tags: @product
2:26.548
Before features/support/hooks.rb:245 0.008
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.330
Then Tails is running from USB drive "old" 0.425
And all tps features are active 2.194
When I write some files expected to persist 2.091
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.602
And all persistent directories from the old Tails version have safe access rights 2.630
And I take note of which tps features are available 0.486
And I shutdown Tails and wait for the computer to power off 3.084
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.221
After features/support/hooks.rb:291 0.129
After features/support/hooks.rb:75 0.010
Tags: @product
2:42.355
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.345
And I log in to a new session 19.035
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.388
And I plug USB drive "to_upgrade" 2.512
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.817
Then the running Tails is installed on USB drive "to_upgrade" 13.729
And I unplug USB drive "to_upgrade" 0.266
And I unplug USB drive "__internal" 0.260
After features/support/hooks.rb:291 7.043
After features/support/hooks.rb:75 0.000
Tags: @product
2:20.978
Before features/support/hooks.rb:245 0.012
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.221
Then all tps features from the old Tails version are active 2.037
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 4.339
And the expected persistent files created with the old Tails version are present in the filesystem 1.685
And all persistent directories from the old Tails version have safe access rights 3.117
After features/support/hooks.rb:291 0.724
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
6:2.725
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.415
And no SquashFS delta is installed 0.159
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.374
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.108
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.414
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.661
When the network is plugged 0.040
And Tor is ready 18.112
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.763
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 11.007
Given I shutdown Tails and wait for the computer to power off 8.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.750
Then Tails is running version 2.2~testoverlayfsng 0.103
And all tps features are active 2.413
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.399
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.269
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.385
When the network is plugged 0.046
And Tor is ready 15.967
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.663
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.027
Given I shutdown Tails and wait for the computer to power off 3.373
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.810
Then Tails is running version 2.3~testoverlayfsng 0.099
And all tps features are active 2.210
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.640
And only the 2.3~testoverlayfsng 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.294
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.327
When the network is plugged 0.036
And Tor is ready 16.120
Then the Upgrader considers the system as up-to-date 0.382
# 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 30.579
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.309
After features/support/hooks.rb:291 0.767
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
27.028
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.972
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.355
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.065
And the signing key used by the Upgrader is outdated 0.502
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 12.429
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.661
After features/support/hooks.rb:291 0.732
After features/support/hooks.rb:75 0.000