Project Number Date
test_Tails_ISO_devel 3207 22 Dec 2023, 15:26

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@automatic_upgrade 43 0 0 0 0 43 2 0 2 6:19.741 Passed
5:52.856
Before features/support/hooks.rb:245 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.388
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.400
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.071
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.424
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.569
When the network is plugged 0.066
And Tor is ready 18.114
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.736
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.253
Given I shutdown Tails and wait for the computer to power off 7.281
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.796
Then Tails is running version 2.2~testoverlayfsng 0.143
And all tps features are active 2.328
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.381
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.302
# 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.328
When the network is plugged 0.044
And Tor is ready 15.039
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.600
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.989
Given I shutdown Tails and wait for the computer to power off 4.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.540
Then Tails is running version 2.3~testoverlayfsng 0.098
And all tps features are active 1.963
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.554
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.061
# 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.253
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.276
When the network is plugged 0.063
And Tor is ready 15.102
Then the Upgrader considers the system as up-to-date 0.255
# 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 25.245
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.521
After features/support/hooks.rb:291 0.777
After features/support/hooks.rb:75 0.016
26.885
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 9.640
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.437
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.100
And the signing key used by the Upgrader is outdated 0.548
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 13.458
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.662
After features/support/hooks.rb:291 1.029
After features/support/hooks.rb:75 0.000