Project Number Date
test_Tails_ISO_devel 3199 18 Dec 2023, 14:48

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 7:45.355 Passed
7:1.156
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 58.157
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.285
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.128
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.447
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.560
When the network is plugged 0.084
And Tor is ready 17.817
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.906
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 12.688
Given I shutdown Tails and wait for the computer to power off 6.426
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.888
Then Tails is running version 2.2~testoverlayfsng 0.124
And all tps features are active 2.550
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.414
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.358
# 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.507
When the network is plugged 0.045
And Tor is ready 18.704
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.913
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.207
Given I shutdown Tails and wait for the computer to power off 4.063
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.399
Then Tails is running version 2.3~testoverlayfsng 0.157
And all tps features are active 4.592
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.601
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.088
# 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.335
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.297
When the network is plugged 0.038
And Tor is ready 15.006
Then the Upgrader considers the system as up-to-date 0.264
# 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 31.215
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.711
After features/support/hooks.rb:291 0.827
After features/support/hooks.rb:75 0.018
44.198
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 22.322
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.416
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.066
And the signing key used by the Upgrader is outdated 1.456
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 16.828
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.062
After features/support/hooks.rb:291 1.027
After features/support/hooks.rb:75 0.000