Project Number Date
test_Tails_ISO_stable 4632 24 Jan 2024, 13:39

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:30.801 Passed
6:3.734
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.957
And no SquashFS delta is installed 0.112
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.156
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.357
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.600
When the network is plugged 0.040
And Tor is ready 16.221
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.589
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.524
Given I shutdown Tails and wait for the computer to power off 10.780
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.044
Then Tails is running version 2.2~testoverlayfsng 0.207
And all tps features are active 2.526
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.407
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.294
# 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.461
When the network is plugged 0.041
And Tor is ready 15.910
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.844
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.009
Given I shutdown Tails and wait for the computer to power off 4.333
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.055
Then Tails is running version 2.3~testoverlayfsng 0.104
And all tps features are active 2.098
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.728
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.082
# 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.285
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.342
When the network is plugged 0.047
And Tor is ready 18.094
Then the Upgrader considers the system as up-to-date 0.281
# 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.167
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.517
After features/support/hooks.rb:291 0.803
After features/support/hooks.rb:75 0.035
27.067
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.363
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.345
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.177
And the signing key used by the Upgrader is outdated 0.641
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 14.789
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.701
After features/support/hooks.rb:291 0.905
After features/support/hooks.rb:75 0.000