Project Number Date
test_Tails_ISO_stable 4662 12 Feb 2024, 14: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 17:45.304 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:14.994
Before features/support/hooks.rb:245 0.006
Given a computer 0.155
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 1:6.729
When I start Tails from USB drive "old" with network unplugged 1:2.954
Then the boot device has safe access rights 3.181
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.271
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:291 3.643
After features/support/hooks.rb:75 0.009
Tags: @product
2:5.953
Before features/support/hooks.rb:245 0.006
Given a computer 0.411
And I start Tails from USB drive "old" with network unplugged and I login 1:8.472
Then Tails is running from USB drive "old" 0.443
And I create a persistent partition 44.956
And I take note of which tps features are available 1.642
Then a Tails persistence partition exists on USB drive "old" 0.946
And I shutdown Tails and wait for the computer to power off 9.079
After features/support/hooks.rb:291 0.157
After features/support/hooks.rb:75 0.011
Tags: @product
2:35.888
Before features/support/hooks.rb:245 0.008
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.106
Then Tails is running from USB drive "old" 0.457
And all tps features are active 2.109
When I write some files expected to persist 1.987
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.316
And all persistence configuration files have safe access rights 0.504
And all persistent directories from the old Tails version have safe access rights 2.844
And I take note of which tps features are available 0.358
And I shutdown Tails and wait for the computer to power off 3.130
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.832
After features/support/hooks.rb:291 0.112
After features/support/hooks.rb:75 0.010
Tags: @product
2:35.993
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.268
And I log in to a new session 15.738
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.026
And I plug USB drive "to_upgrade" 2.471
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.385
Then the running Tails is installed on USB drive "to_upgrade" 13.720
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:291 1.602
After features/support/hooks.rb:75 0.000
Tags: @product
1:56.105
Before features/support/hooks.rb:245 0.005
Given a computer 0.135
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.288
Then all tps features from the old Tails version are active 1.415
And Tails is running from USB drive "to_upgrade" 0.398
And the boot device has safe access rights 3.557
And the expected persistent files created with the old Tails version are present in the filesystem 1.632
And all persistent directories from the old Tails version have safe access rights 2.676
After features/support/hooks.rb:291 0.662
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
5:48.582
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.508
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.315
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.075
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.402
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.547
When the network is plugged 0.029
And Tor is ready 18.380
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.702
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.344
Given I shutdown Tails and wait for the computer to power off 6.485
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.582
Then Tails is running version 2.2~testoverlayfsng 0.112
And all tps features are active 1.732
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.374
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.331
When the network is plugged 0.021
And Tor is ready 14.834
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.509
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.890
Given I shutdown Tails and wait for the computer to power off 4.448
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.337
Then Tails is running version 2.3~testoverlayfsng 0.117
And all tps features are active 1.681
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.631
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.062
# 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.284
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.301
When the network is plugged 0.022
And Tor is ready 14.881
Then the Upgrader considers the system as up-to-date 0.287
# 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 26.381
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.432
After features/support/hooks.rb:291 0.746
After features/support/hooks.rb:75 0.024
Tags: @product @automatic_upgrade
27.785
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.713
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.309
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.063
And the signing key used by the Upgrader is outdated 1.300
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 13.645
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.699
After features/support/hooks.rb:291 0.704
After features/support/hooks.rb:75 0.000