Project Number Date
test_Tails_ISO_stable 4615 11 Jan 2024, 15:42

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:42.262 Passed
6:12.941
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.553
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.348
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.134
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.320
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.592
When the network is plugged 0.032
And Tor is ready 16.543
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.630
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.291
Given I shutdown Tails and wait for the computer to power off 5.340
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.280
Then Tails is running version 2.2~testoverlayfsng 0.094
And all tps features are active 2.130
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.395
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.250
# 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.264
When the network is plugged 0.055
And Tor is ready 44.881
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.550
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.874
Given I shutdown Tails and wait for the computer to power off 3.101
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.835
Then Tails is running version 2.3~testoverlayfsng 0.099
And all tps features are active 2.135
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.506
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.062
# 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.288
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.272
When the network is plugged 0.049
And Tor is ready 16.746
Then the Upgrader considers the system as up-to-date 0.244
# 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.844
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.012
After features/support/hooks.rb:291 0.811
After features/support/hooks.rb:75 0.017
29.321
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 9.576
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.425
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.064
And the signing key used by the Upgrader is outdated 1.031
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 16.587
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.596
After features/support/hooks.rb:291 0.738
After features/support/hooks.rb:75 0.000