Project Number Date
test_Tails_ISO_stable 4560 09 Dec 2023, 12:15

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:23.386 Passed
5:52.875
Before features/support/hooks.rb:245 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.961
And no SquashFS delta is installed 0.136
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.375
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.108
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.326
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.516
When the network is plugged 0.049
And Tor is ready 18.381
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.595
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.346
Given I shutdown Tails and wait for the computer to power off 7.101
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.821
Then Tails is running version 2.2~testoverlayfsng 0.105
And all tps features are active 2.134
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.392
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.275
# 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.300
When the network is plugged 0.038
And Tor is ready 13.386
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 4.092
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.719
Given I shutdown Tails and wait for the computer to power off 4.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.583
Then Tails is running version 2.3~testoverlayfsng 0.120
And all tps features are active 2.164
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.578
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.077
# 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.330
When the network is plugged 0.035
And Tor is ready 16.474
Then the Upgrader considers the system as up-to-date 0.286
# 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.723
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.602
After features/support/hooks.rb:291 0.850
After features/support/hooks.rb:75 0.023
30.511
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.141
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.312
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.058
And the signing key used by the Upgrader is outdated 0.549
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 15.692
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.723
After features/support/hooks.rb:291 1.161
After features/support/hooks.rb:75 0.000