Project Number Date
test_Tails_ISO_devel 3200 18 Dec 2023, 18:30

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:17.744 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.190
Before features/support/hooks.rb:245 0.007
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 19.006
When I start Tails from USB drive "old" with network unplugged 1:6.764
Then the boot device has safe access rights 3.187
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.261
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:291 3.557
After features/support/hooks.rb:75 0.012
Tags: @product
1:58.277
Before features/support/hooks.rb:245 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:4.705
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 43.709
And I take note of which tps features are available 1.316
Then a Tails persistence partition exists on USB drive "old" 0.901
And I shutdown Tails and wait for the computer to power off 7.101
After features/support/hooks.rb:291 0.143
After features/support/hooks.rb:75 0.011
Tags: @product
2:26.964
Before features/support/hooks.rb:245 0.007
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.135
Then Tails is running from USB drive "old" 0.357
And all tps features are active 2.136
When I write some files expected to persist 1.782
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.654
And all persistent directories from the old Tails version have safe access rights 2.709
And I take note of which tps features are available 0.483
And I shutdown Tails and wait for the computer to power off 3.074
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.190
After features/support/hooks.rb:291 0.101
After features/support/hooks.rb:75 0.011
Tags: @product
2:36.568
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 12.174
And I log in to a new session 15.980
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.904
And I plug USB drive "to_upgrade" 2.491
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.980
Then the running Tails is installed on USB drive "to_upgrade" 13.650
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:291 3.527
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.581
Before features/support/hooks.rb:245 0.009
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.173
Then all tps features from the old Tails version are active 1.882
And Tails is running from USB drive "to_upgrade" 0.455
And the boot device has safe access rights 4.026
And the expected persistent files created with the old Tails version are present in the filesystem 1.729
And all persistent directories from the old Tails version have safe access rights 3.111
After features/support/hooks.rb:291 0.677
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
6:9.254
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.710
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.478
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.083
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.387
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.559
When the network is plugged 0.046
And Tor is ready 16.520
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.671
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.993
Given I shutdown Tails and wait for the computer to power off 6.245
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.198
Then Tails is running version 2.2~testoverlayfsng 0.105
And all tps features are active 2.350
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.459
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.291
When the network is plugged 0.039
And Tor is ready 15.414
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.713
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.927
Given I shutdown Tails and wait for the computer to power off 3.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.564
Then Tails is running version 2.3~testoverlayfsng 0.136
And all tps features are active 2.318
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.716
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.081
# 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.315
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.275
When the network is plugged 0.033
And Tor is ready 14.981
Then the Upgrader considers the system as up-to-date 10.834
# 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 28.536
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.442
After features/support/hooks.rb:291 0.707
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
29.907
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 10.615
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.461
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.120
And the signing key used by the Upgrader is outdated 1.588
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 15.469
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.599
After features/support/hooks.rb:291 0.782
After features/support/hooks.rb:75 0.000