Project Number Date
test_Tails_ISO_stable 4612 10 Jan 2024, 19:26

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:46.309 Passed
6:19.716
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 28.389
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.292
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.060
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.392
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.593
When the network is plugged 0.043
And Tor is ready 16.827
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.764
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.685
Given I shutdown Tails and wait for the computer to power off 8.469
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.354
Then Tails is running version 2.2~testoverlayfsng 0.128
And all tps features are active 2.682
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.447
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.288
# 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.371
When the network is plugged 0.042
And Tor is ready 20.634
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.629
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.209
Given I shutdown Tails and wait for the computer to power off 4.079
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.286
Then Tails is running version 2.3~testoverlayfsng 0.128
And all tps features are active 2.498
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.609
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.098
# 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.330
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.417
When the network is plugged 0.049
And Tor is ready 17.462
Then the Upgrader considers the system as up-to-date 0.466
# 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.452
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.349
After features/support/hooks.rb:291 0.772
After features/support/hooks.rb:75 0.025
26.593
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.477
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.361
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.541
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 13.374
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.729
After features/support/hooks.rb:291 1.203
After features/support/hooks.rb:75 0.000