Project Number Date
test_Tails_ISO_stable 4546 02 Dec 2023, 12:06

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:21.325 Passed
5:50.825
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.774
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.426
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.099
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.446
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.627
When the network is plugged 0.047
And Tor is ready 17.535
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.783
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.639
Given I shutdown Tails and wait for the computer to power off 6.339
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.332
Then Tails is running version 2.2~testoverlayfsng 0.105
And all tps features are active 2.266
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.374
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.285
When the network is plugged 0.039
And Tor is ready 15.582
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.623
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.976
Given I shutdown Tails and wait for the computer to power off 3.428
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.780
Then Tails is running version 2.3~testoverlayfsng 0.119
And all tps features are active 2.039
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.675
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.106
# 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.291
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.294
When the network is plugged 0.051
And Tor is ready 16.298
Then the Upgrader considers the system as up-to-date 0.302
# 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.460
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.158
After features/support/hooks.rb:291 0.804
After features/support/hooks.rb:75 0.030
30.499
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 9.790
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.315
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.201
And the signing key used by the Upgrader is outdated 1.587
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 15.753
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.773
After features/support/hooks.rb:291 0.696
After features/support/hooks.rb:75 0.000