From 211de6d6641f38d6019e48ff71aa63c2c7e35b66 Mon Sep 17 00:00:00 2001 From: Florian Bruhin Date: Tue, 10 Oct 2017 20:28:31 +0200 Subject: [PATCH] Leave qute://settings after tests are done Let's see whether this helps with the flakyness where the next test (for pyeval) tries to set frame_flattening... --- tests/end2end/features/qutescheme.feature | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tests/end2end/features/qutescheme.feature b/tests/end2end/features/qutescheme.feature index c60e18f3a..b36601377 100644 --- a/tests/end2end/features/qutescheme.feature +++ b/tests/end2end/features/qutescheme.feature @@ -86,6 +86,7 @@ Feature: Special qute:// pages # an explicit Tab to unfocus the input field seems to stabilize the tests And I press the key "" And I wait for "Config option changed: ignore_case *" in the log + And I open about:blank Then the option ignore_case should be set to always Scenario: Focusing input fields in qute://settings and entering invalid value @@ -99,6 +100,7 @@ Feature: Special qute:// pages And I press the key "" # an explicit Tab to unfocus the input field seems to stabilize the tests And I press the key "" + And I open about:blank Then "Invalid value 'foo' *" should be logged # pdfjs support