diff options
| -rw-r--r-- | .github/workflows/ci.yml | 1 | ||||
| -rw-r--r-- | doc/contributing.asciidoc | 11 |
2 files changed, 10 insertions, 2 deletions
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index f52d7fdba..8721699ad 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -82,7 +82,6 @@ jobs: container: image: "qutebrowser/ci:${{ matrix.image }}" env: - QUTE_BDD_WEBENGINE: "${{ matrix.image != 'archlinux-webkit' }}" DOCKER: "${{ matrix.image }}" CI: true PYTEST_ADDOPTS: "--color=yes" diff --git a/doc/contributing.asciidoc b/doc/contributing.asciidoc index 70447d8c5..35a72878e 100644 --- a/doc/contributing.asciidoc +++ b/doc/contributing.asciidoc @@ -153,7 +153,7 @@ smallest scope which makes sense. Most of the time, this will be line scope. false-positives, let me know! I'm still tweaking the parameters. -Running Specific Tests +Running specific tests ~~~~~~~~~~~~~~~~~~~~~~ While you are developing you often don't want to run the full test @@ -180,6 +180,15 @@ tox -e py37 -- tests/end2end/features/test_tabs_bdd.py -k undo tox -e py37-cov -- tests/unit/browser/test_webelem.py ---- +Specifying the backend for tests +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Tests automatically pick the backend based on what they manage to import. If +you have both backends available and you would like the tests to be run with a +specific one you can set either of a) the environment variable QUTE_TESTS_BACKEND +, or b) the command line argument --qute-backend, to the desired backend +(webkit/webengine). + Profiling ~~~~~~~~~ |