Project Number Date
test_Tails_ISO_stable 4611 10 Jan 2024, 17:11

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:37.881 Passed
6:6.976
Before features/support/hooks.rb:245 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.768
And no SquashFS delta is installed 0.150
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.439
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.053
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.415
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.599
When the network is plugged 0.047
And Tor is ready 16.360
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.858
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.218
Given I shutdown Tails and wait for the computer to power off 6.426
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.496
Then Tails is running version 2.2~testoverlayfsng 0.174
And all tps features are active 5.488
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.402
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.348
When the network is plugged 0.043
And Tor is ready 18.212
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.103
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.355
Given I shutdown Tails and wait for the computer to power off 4.345
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.496
Then Tails is running version 2.3~testoverlayfsng 0.102
And all tps features are active 3.093
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.605
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.284
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.306
When the network is plugged 0.038
And Tor is ready 16.722
Then the Upgrader considers the system as up-to-date 0.285
# 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.377
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.878
After features/support/hooks.rb:291 0.883
After features/support/hooks.rb:75 0.021
30.904
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 12.351
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.365
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.077
And the signing key used by the Upgrader is outdated 1.064
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 13.732
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.262
After features/support/hooks.rb:291 0.772
After features/support/hooks.rb:75 0.000