Project Number Date
test_Tails_ISO_stable 4650 01 Feb 2024, 18: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:31.741 Passed
6:2.961
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.186
And no SquashFS delta is installed 0.429
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.379
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.068
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.473
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.691
When the network is plugged 0.060
And Tor is ready 18.090
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.676
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.985
Given I shutdown Tails and wait for the computer to power off 6.360
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.966
Then Tails is running version 2.2~testoverlayfsng 0.113
And all tps features are active 1.956
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.415
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.109
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.297
# 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.380
When the network is plugged 0.064
And Tor is ready 15.223
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.931
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.141
Given I shutdown Tails and wait for the computer to power off 4.100
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.744
Then Tails is running version 2.3~testoverlayfsng 0.108
And all tps features are active 2.065
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.553
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.089
# 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.312
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.306
When the network is plugged 0.057
And Tor is ready 15.672
Then the Upgrader considers the system as up-to-date 0.318
# 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.670
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.958
After features/support/hooks.rb:291 0.811
After features/support/hooks.rb:75 0.018
28.780
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.379
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.417
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.080
And the signing key used by the Upgrader is outdated 0.820
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 14.995
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.018
After features/support/hooks.rb:291 0.938
After features/support/hooks.rb:75 0.000