Project Number Date
test_Tails_ISO_devel 3223 05 Jan 2024, 12:16

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:29.032 Passed
6:1.701
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.347
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.536
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.515
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.606
When the network is plugged 0.054
And Tor is ready 20.417
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.732
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.856
Given I shutdown Tails and wait for the computer to power off 6.349
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.692
Then Tails is running version 2.2~testoverlayfsng 0.110
And all tps features are active 2.438
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.441
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.063
# 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.384
When the network is plugged 0.095
And Tor is ready 14.770
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.851
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.363
Given I shutdown Tails and wait for the computer to power off 4.365
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.415
Then Tails is running version 2.3~testoverlayfsng 0.103
And all tps features are active 2.290
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.624
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.073
# 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.288
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.319
When the network is plugged 0.045
And Tor is ready 14.983
Then the Upgrader considers the system as up-to-date 0.288
# 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 24.871
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.942
After features/support/hooks.rb:291 0.862
After features/support/hooks.rb:75 0.020
27.331
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 9.732
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.332
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.053
And the signing key used by the Upgrader is outdated 0.678
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 12.829
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.672
After features/support/hooks.rb:291 0.927
After features/support/hooks.rb:75 0.000