Project Number Date
test_Tails_ISO_devel 3194 14 Dec 2023, 12:11

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 15:47.758 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:20.482
Before features/support/hooks.rb:245 0.007
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 19.765
When I start Tails from USB drive "old" with network unplugged 55.630
Then the boot device has safe access rights 2.909
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:291 3.512
After features/support/hooks.rb:75 0.010
Tags: @product
1:59.536
Before features/support/hooks.rb:245 0.007
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:5.252
Then Tails is running from USB drive "old" 0.608
And I create a persistent partition 42.946
And I take note of which tps features are available 1.466
Then a Tails persistence partition exists on USB drive "old" 0.819
And I shutdown Tails and wait for the computer to power off 8.249
After features/support/hooks.rb:291 0.204
After features/support/hooks.rb:75 0.013
Tags: @product
2:15.568
Before features/support/hooks.rb:245 0.008
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:47.895
Then Tails is running from USB drive "old" 0.325
And all tps features are active 2.149
When I write some files expected to persist 1.763
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.599
And all persistent directories from the old Tails version have safe access rights 2.854
And I take note of which tps features are available 0.498
And I shutdown Tails and wait for the computer to power off 3.065
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.985
After features/support/hooks.rb:291 0.106
After features/support/hooks.rb:75 0.008
Tags: @product
2:32.173
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 10.016
And I log in to a new session 15.964
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.135
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.927
Then the running Tails is installed on USB drive "to_upgrade" 14.273
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.184
After features/support/hooks.rb:291 6.502
After features/support/hooks.rb:75 0.000
Tags: @product
1:52.333
Before features/support/hooks.rb:245 0.007
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:42.336
Then all tps features from the old Tails version are active 1.590
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 3.508
And the expected persistent files created with the old Tails version are present in the filesystem 1.519
And all persistent directories from the old Tails version have safe access rights 2.891
After features/support/hooks.rb:291 0.663
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:23.760
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 10.154
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.291
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.055
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.398
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.586
When the network is plugged 0.039
And Tor is ready 14.422
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.576
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.660
Given I shutdown Tails and wait for the computer to power off 5.285
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.207
Then Tails is running version 2.2~testoverlayfsng 0.102
And all tps features are active 2.388
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.377
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.276
# 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.274
When the network is plugged 0.034
And Tor is ready 14.485
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.760
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.726
Given I shutdown Tails and wait for the computer to power off 4.275
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.292
Then Tails is running version 2.3~testoverlayfsng 0.098
And all tps features are active 2.060
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.617
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.085
# 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.299
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.340
When the network is plugged 0.043
And Tor is ready 13.895
Then the Upgrader considers the system as up-to-date 0.282
# 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.534
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.664
After features/support/hooks.rb:291 0.746
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
23.904
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 9.268
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.373
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.056
And the signing key used by the Upgrader is outdated 0.478
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 11.963
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.667
After features/support/hooks.rb:291 0.646
After features/support/hooks.rb:75 0.000