Project Number Date
test_Tails_ISO_stable 4586 22 Dec 2023, 14:24

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:17.940 Passed
5:50.824
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.584
And no SquashFS delta is installed 0.163
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.327
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.053
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.349
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.549
When the network is plugged 0.044
And Tor is ready 17.551
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.961
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.690
Given I shutdown Tails and wait for the computer to power off 6.262
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.226
Then Tails is running version 2.2~testoverlayfsng 0.131
And all tps features are active 2.510
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.428
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.300
# 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.320
When the network is plugged 0.043
And Tor is ready 17.099
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.639
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.041
Given I shutdown Tails and wait for the computer to power off 3.298
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.374
Then Tails is running version 2.3~testoverlayfsng 0.099
And all tps features are active 2.180
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.562
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.079
# 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.272
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.291
When the network is plugged 0.038
And Tor is ready 18.104
Then the Upgrader considers the system as up-to-date 0.508
# 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.886
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.786
After features/support/hooks.rb:291 1.012
After features/support/hooks.rb:75 0.020
27.115
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.380
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.309
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.058
And the signing key used by the Upgrader is outdated 1.943
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 13.827
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.554
After features/support/hooks.rb:291 0.647
After features/support/hooks.rb:75 0.000