Project Number Date
test_Tails_ISO_devel 3252 25 Jan 2024, 13:07

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:32.073 Passed
5:59.961
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 12.629
And no SquashFS delta is installed 0.177
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.342
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.084
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.435
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.637
When the network is plugged 0.316
And Tor is ready 19.702
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.790
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.013
Given I shutdown Tails and wait for the computer to power off 7.261
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.059
Then Tails is running version 2.2~testoverlayfsng 0.103
And all tps features are active 4.947
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.403
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.299
# 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.204
And Tor is ready 14.642
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 4.232
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.514
Given I shutdown Tails and wait for the computer to power off 3.609
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.608
Then Tails is running version 2.3~testoverlayfsng 0.112
And all tps features are active 3.614
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.610
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.082
# 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.332
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.307
When the network is plugged 0.047
And Tor is ready 16.244
Then the Upgrader considers the system as up-to-date 0.260
# 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.574
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.373
After features/support/hooks.rb:291 0.733
After features/support/hooks.rb:75 0.021
32.112
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.048
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.324
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.168
And the signing key used by the Upgrader is outdated 1.355
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 17.434
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.745
After features/support/hooks.rb:291 0.940
After features/support/hooks.rb:75 0.000