Project Number Date
test_Tails_ISO_stable 4661 11 Feb 2024, 15:03

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:30.591 Passed
6:3.287
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.014
And no SquashFS delta is installed 0.140
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.428
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.051
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.364
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.585
When the network is plugged 0.055
And Tor is ready 15.740
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.765
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.687
Given I shutdown Tails and wait for the computer to power off 5.351
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.351
Then Tails is running version 2.2~testoverlayfsng 0.104
And all tps features are active 1.836
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.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.293
When the network is plugged 0.021
And Tor is ready 13.782
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.035
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.736
Given I shutdown Tails and wait for the computer to power off 3.416
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.480
Then Tails is running version 2.3~testoverlayfsng 0.112
And all tps features are active 1.726
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.668
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.067
# 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.292
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.331
When the network is plugged 0.018
And Tor is ready 16.153
Then the Upgrader considers the system as up-to-date 10.724
# 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.794
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.344
After features/support/hooks.rb:291 0.780
After features/support/hooks.rb:75 0.054
27.304
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.245
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.496
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.060
And the signing key used by the Upgrader is outdated 0.485
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 14.132
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.858
After features/support/hooks.rb:291 0.803
After features/support/hooks.rb:75 0.000