Project Number Date
test_Tails_ISO_stable 4660 10 Feb 2024, 14:57

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:37.389 Passed
6:9.881
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 11.455
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.357
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.077
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.443
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.551
When the network is plugged 0.028
And Tor is ready 14.686
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.648
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.635
Given I shutdown Tails and wait for the computer to power off 6.531
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.991
Then Tails is running version 2.2~testoverlayfsng 0.108
And all tps features are active 2.476
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.371
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.367
# 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.281
When the network is plugged 0.034
And Tor is ready 17.720
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.206
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.073
Given I shutdown Tails and wait for the computer to power off 4.282
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.068
Then Tails is running version 2.3~testoverlayfsng 0.126
And all tps features are active 1.916
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.581
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.069
# 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.320
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.309
When the network is plugged 0.041
And Tor is ready 15.756
Then the Upgrader considers the system as up-to-date 0.292
# 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 29.602
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.306
After features/support/hooks.rb:291 0.727
After features/support/hooks.rb:75 0.049
27.508
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.086
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.356
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 0.567
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 15.749
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.648
After features/support/hooks.rb:291 0.688
After features/support/hooks.rb:75 0.000