rnhmjoj/qutebrowser
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Leave qute://settings after tests are done

Browse Source 
Let's see whether this helps with the flakyness where the next test (for pyeval)
tries to set frame_flattening...
This commit is contained in:
Florian Bruhin 2017-10-10 20:28:31 +02:00
parent 0afbcc0faa
commit 211de6d664
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
tests/end2end/features/qutescheme.feature
View File

@ -86,6 +86,7 @@ Feature: Special qute:// pages
# an explicit Tab to unfocus the input field seems to stabilize the tests # an explicit Tab to unfocus the input field seems to stabilize the tests
And I press the key "<Tab>" And I press the key "<Tab>"
And I wait for "Config option changed: ignore_case *" in the log 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 Then the option ignore_case should be set to always
Scenario: Focusing input fields in qute://settings and entering invalid value Scenario: Focusing input fields in qute://settings and entering invalid value
@ -99,6 +100,7 @@ Feature: Special qute:// pages
And I press the key "<Escape>" And I press the key "<Escape>"
# an explicit Tab to unfocus the input field seems to stabilize the tests # an explicit Tab to unfocus the input field seems to stabilize the tests
And I press the key "<Tab>" And I press the key "<Tab>"
And I open about:blank
Then "Invalid value 'foo' *" should be logged Then "Invalid value 'foo' *" should be logged
# pdfjs support # pdfjs support