Project Number Date
test_Tails_ISO_devel 3221 03 Jan 2024, 12:15

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.361 Passed
6:1.306
Before features/support/hooks.rb:245 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.343
And no SquashFS delta is installed 0.149
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.327
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.069
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.371
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.560
When the network is plugged 0.193
And Tor is ready 17.527
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.932
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.196
Given I shutdown Tails and wait for the computer to power off 6.376
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.291
Then Tails is running version 2.2~testoverlayfsng 0.104
And all tps features are active 2.395
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.378
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.415
When the network is plugged 0.037
And Tor is ready 14.635
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.804
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.866
Given I shutdown Tails and wait for the computer to power off 4.313
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.021
Then Tails is running version 2.3~testoverlayfsng 0.116
And all tps features are active 2.094
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.656
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.079
# 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.273
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.299
When the network is plugged 0.044
And Tor is ready 15.620
Then the Upgrader considers the system as up-to-date 0.300
# 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 27.676
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.457
After features/support/hooks.rb:291 0.855
After features/support/hooks.rb:75 0.018
29.054
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.763
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.413
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.591
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 16.467
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.723
After features/support/hooks.rb:291 1.307
After features/support/hooks.rb:75 0.000