Commit 05ce1235 authored by intrigeri's avatar intrigeri
Browse files

Test suite: fix testing the Unsafe Browser after automatic upgrade (refs: #15286)

The Unsafe Browser needs a DNS resolver configured so we need to plug
the network first.
parent 8f32f322
......@@ -138,9 +138,13 @@ Feature: Upgrading an old Tails USB installation
And all persistence presets are enabled
And the file system changes introduced in version 2.3~test are present
And only the 2.3~test SquashFS delta is installed
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized
# 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
Then the file system changes introduced in version 2.3~test are present in the Unsafe Browser's chroot
When the network is plugged
And Tor is ready
Then I successfully start the Unsafe Browser
And the file system changes introduced in version 2.3~test are present in the Unsafe Browser's chroot
@automatic_upgrade
Scenario: Upgrading a Tails that has several SquashFS deltas present with an incremental upgrade
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment