Project Number Date
test_Tails_ISO_stable 4578 20 Dec 2023, 12:14

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:35.863 Passed
6:5.988
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.551
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.422
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.094
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.587
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.574
When the network is plugged 0.036
And Tor is ready 16.798
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.780
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.653
Given I shutdown Tails and wait for the computer to power off 6.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.061
Then Tails is running version 2.2~testoverlayfsng 0.115
And all tps features are active 2.605
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.442
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.376
When the network is plugged 0.045
And Tor is ready 15.233
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 4.110
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.119
Given I shutdown Tails and wait for the computer to power off 4.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.976
Then Tails is running version 2.3~testoverlayfsng 0.111
And all tps features are active 2.425
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.642
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.096
# 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.279
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.314
When the network is plugged 0.044
And Tor is ready 17.804
Then the Upgrader considers the system as up-to-date 0.247
# 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.717
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.484
After features/support/hooks.rb:291 0.830
After features/support/hooks.rb:75 0.021
29.874
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.309
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.387
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.044
And the signing key used by the Upgrader is outdated 0.501
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 14.782
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.797
After features/support/hooks.rb:291 0.926
After features/support/hooks.rb:75 0.000