Project Number Date
test_Tails_ISO_devel 3261 30 Jan 2024, 17: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 7:2.673 Passed
6:33.056
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 14.189
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.359
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.090
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.449
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.527
When the network is plugged 0.035
And Tor is ready 45.164
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.551
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.169
Given I shutdown Tails and wait for the computer to power off 6.160
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.277
Then Tails is running version 2.2~testoverlayfsng 0.113
And all tps features are active 2.439
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.371
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.353
# 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.349
When the network is plugged 0.030
And Tor is ready 16.081
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.893
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.186
Given I shutdown Tails and wait for the computer to power off 3.537
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.482
Then Tails is running version 2.3~testoverlayfsng 0.104
And all tps features are active 2.232
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.581
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.101
# 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.294
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.334
When the network is plugged 0.045
And Tor is ready 15.530
Then the Upgrader considers the system as up-to-date 10.787
# 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 28.015
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.983
After features/support/hooks.rb:291 1.017
After features/support/hooks.rb:75 0.036
29.617
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.682
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.333
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.067
And the signing key used by the Upgrader is outdated 1.308
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 15.452
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.718
After features/support/hooks.rb:291 1.188
After features/support/hooks.rb:75 0.000