Project Number Date
test_Tails_ISO_stable 4656 08 Feb 2024, 13:03

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:5.682 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:31.414
Before features/support/hooks.rb:245 0.006
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.077
And I write an old version of the Tails USB image to disk "old" 19.975
When I start Tails from USB drive "old" with network unplugged 1:5.716
Then the boot device has safe access rights 3.294
And Tails is running from USB drive "old" 0.395
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.076
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.218
After features/support/hooks.rb:291 3.605
After features/support/hooks.rb:75 0.011
Tags: @product
2:3.019
Before features/support/hooks.rb:245 0.007
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:6.986
Then Tails is running from USB drive "old" 0.415
And I create a persistent partition 43.930
And I take note of which tps features are available 1.551
Then a Tails persistence partition exists on USB drive "old" 0.833
And I shutdown Tails and wait for the computer to power off 9.102
After features/support/hooks.rb:291 0.150
After features/support/hooks.rb:75 0.010
Tags: @product
2:26.974
Before features/support/hooks.rb:245 0.006
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.405
Then Tails is running from USB drive "old" 0.326
And all tps features are active 1.882
When I write some files expected to persist 1.906
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 2.679
And I take note of which tps features are available 0.638
And I shutdown Tails and wait for the computer to power off 3.061
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.175
After features/support/hooks.rb:291 0.105
After features/support/hooks.rb:75 0.009
Tags: @product
2:33.344
Before features/support/hooks.rb:245 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 10.364
And I log in to a new session 17.298
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.109
And I plug USB drive "to_upgrade" 2.486
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.393
Then the running Tails is installed on USB drive "to_upgrade" 12.312
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:291 0.848
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.016
Before features/support/hooks.rb:245 0.005
Given a computer 0.166
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.407
Then all tps features from the old Tails version are active 1.768
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.658
And the expected persistent files created with the old Tails version are present in the filesystem 1.620
And all persistent directories from the old Tails version have safe access rights 3.076
After features/support/hooks.rb:291 0.631
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
6:2.521
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.070
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.453
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.076
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.445
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.639
When the network is plugged 0.041
And Tor is ready 17.732
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.858
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.563
Given I shutdown Tails and wait for the computer to power off 5.244
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.088
Then Tails is running version 2.2~testoverlayfsng 0.122
And all tps features are active 2.231
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.375
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.313
When the network is plugged 0.033
And Tor is ready 15.570
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.075
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.670
Given I shutdown Tails and wait for the computer to power off 4.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.376
Then Tails is running version 2.3~testoverlayfsng 0.125
And all tps features are active 2.357
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.570
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.100
# 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.349
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.348
When the network is plugged 0.038
And Tor is ready 16.554
Then the Upgrader considers the system as up-to-date 0.462
# 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.357
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.507
After features/support/hooks.rb:291 0.866
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
29.392
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.096
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.460
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.098
And the signing key used by the Upgrader is outdated 0.645
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 16.324
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.715
After features/support/hooks.rb:291 0.974
After features/support/hooks.rb:75 0.000