Project Number Date
test_Tails_ISO_devel 3201 19 Dec 2023, 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:21.436 Passed
5:54.216
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 10.525
And no SquashFS delta is installed 0.175
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.298
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.336
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.645
When the network is plugged 0.043
And Tor is ready 17.712
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.183
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.758
Given I shutdown Tails and wait for the computer to power off 5.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.357
Then Tails is running version 2.2~testoverlayfsng 0.101
And all tps features are active 2.148
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.333
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.265
# 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.283
When the network is plugged 0.045
And Tor is ready 14.361
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.608
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.611
Given I shutdown Tails and wait for the computer to power off 4.288
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.786
Then Tails is running version 2.3~testoverlayfsng 0.089
And all tps features are active 2.064
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.058
# 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.281
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.275
When the network is plugged 0.044
And Tor is ready 14.520
Then the Upgrader considers the system as up-to-date 10.749
# 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.144
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 3.094
After features/support/hooks.rb:291 0.818
After features/support/hooks.rb:75 0.024
27.220
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 9.755
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.348
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.073
And the signing key used by the Upgrader is outdated 1.263
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 13.087
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.646
After features/support/hooks.rb:291 0.664
After features/support/hooks.rb:75 0.000