Project Number Date
test_Tails_ISO_stable 4628 22 Jan 2024, 15:46

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:56.448 Passed
6:28.012
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 12.295
And no SquashFS delta is installed 0.130
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.349
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.082
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.501
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.652
When the network is plugged 0.034
And Tor is ready 18.364
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.659
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.637
Given I shutdown Tails and wait for the computer to power off 6.300
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.303
Then Tails is running version 2.2~testoverlayfsng 0.106
And all tps features are active 2.219
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.405
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.033
And Tor is ready 45.478
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.580
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.263
Given I shutdown Tails and wait for the computer to power off 4.079
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.660
Then Tails is running version 2.3~testoverlayfsng 0.132
And all tps features are active 2.144
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.605
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.076
# 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.309
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.365
When the network is plugged 0.039
And Tor is ready 18.482
Then the Upgrader considers the system as up-to-date 0.296
# 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.183
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.567
After features/support/hooks.rb:291 0.835
After features/support/hooks.rb:75 0.026
28.436
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 10.180
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.509
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.092
And the signing key used by the Upgrader is outdated 0.663
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 15.249
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.687
After features/support/hooks.rb:291 0.663
After features/support/hooks.rb:75 0.000