Project Number Date
test_Tails_ISO_stable 4657 08 Feb 2024, 19:02

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:48.153 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:26.777
Before features/support/hooks.rb:245 0.005
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 17.843
When I start Tails from USB drive "old" with network unplugged 1:3.633
Then the boot device has safe access rights 3.071
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.073
And udev-watchdog is monitoring the correct device 0.272
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:291 3.530
After features/support/hooks.rb:75 0.009
Tags: @product
2:18.517
Before features/support/hooks.rb:245 0.007
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:24.504
Then Tails is running from USB drive "old" 0.457
And I create a persistent partition 43.858
And I take note of which tps features are available 1.463
Then a Tails persistence partition exists on USB drive "old" 0.926
And I shutdown Tails and wait for the computer to power off 7.082
After features/support/hooks.rb:291 0.134
After features/support/hooks.rb:75 0.011
Tags: @product
2:28.196
Before features/support/hooks.rb:245 0.007
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:58.216
Then Tails is running from USB drive "old" 0.522
And all tps features are active 2.156
When I write some files expected to persist 2.408
# 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.484
And all persistent directories from the old Tails version have safe access rights 2.987
And I take note of which tps features are available 1.388
And I shutdown Tails and wait for the computer to power off 3.060
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.504
After features/support/hooks.rb:291 0.172
After features/support/hooks.rb:75 0.010
Tags: @product
2:41.085
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 12.101
And I log in to a new session 19.792
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.400
And I plug USB drive "to_upgrade" 2.485
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.825
Then the running Tails is installed on USB drive "to_upgrade" 14.007
And I unplug USB drive "to_upgrade" 0.252
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:291 7.481
After features/support/hooks.rb:75 0.000
Tags: @product
2:9.792
Before features/support/hooks.rb:245 0.007
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.589
Then all tps features from the old Tails version are active 2.245
And Tails is running from USB drive "to_upgrade" 0.421
And the boot device has safe access rights 4.264
And the expected persistent files created with the old Tails version are present in the filesystem 1.899
And all persistent directories from the old Tails version have safe access rights 3.175
After features/support/hooks.rb:291 0.930
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:14.663
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 11.427
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.399
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.084
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.528
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.732
When the network is plugged 0.045
And Tor is ready 17.592
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.944
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.800
Given I shutdown Tails and wait for the computer to power off 6.290
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.043
Then Tails is running version 2.2~testoverlayfsng 0.106
And all tps features are active 2.237
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.419
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.297
# 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.322
When the network is plugged 0.043
And Tor is ready 16.025
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.987
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.941
Given I shutdown Tails and wait for the computer to power off 4.498
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.612
Then Tails is running version 2.3~testoverlayfsng 0.100
And all tps features are active 2.232
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.722
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.089
# 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.312
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.352
When the network is plugged 0.031
And Tor is ready 16.901
Then the Upgrader considers the system as up-to-date 10.821
# 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 27.021
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.485
After features/support/hooks.rb:291 0.856
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
29.119
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.736
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.379
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 0.578
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 15.605
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.719
After features/support/hooks.rb:291 0.964
After features/support/hooks.rb:75 0.000