Project Number Date
test_Tails_ISO_stable 4592 26 Dec 2023, 12:04

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:24.925 Passed
5:58.296
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.921
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.325
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.078
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.370
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.501
When the network is plugged 0.039
And Tor is ready 16.758
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.618
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.072
Given I shutdown Tails and wait for the computer to power off 5.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.384
Then Tails is running version 2.2~testoverlayfsng 0.103
And all tps features are active 2.282
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.453
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.283
# 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.313
When the network is plugged 0.044
And Tor is ready 17.059
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.743
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.928
Given I shutdown Tails and wait for the computer to power off 4.309
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.015
Then Tails is running version 2.3~testoverlayfsng 0.098
And all tps features are active 2.074
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.572
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.099
# 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.304
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.310
When the network is plugged 0.042
And Tor is ready 16.609
Then the Upgrader considers the system as up-to-date 0.265
# 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.404
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.449
After features/support/hooks.rb:291 0.675
After features/support/hooks.rb:75 0.018
26.628
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.519
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.319
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.557
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 13.410
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.724
After features/support/hooks.rb:291 1.150
After features/support/hooks.rb:75 0.000