You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/contribute-to-core-lightning/testing.md
+26-8Lines changed: 26 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,10 @@ There are four kinds of tests:
43
43
44
44
You can also append `-k TESTNAME` to run a single test. Environment variables `DEBUG_SUBD=<subdaemon>` and `TIMEOUT=<seconds>` can be useful for debugging subdaemons on individual tests, and `DEBUG_LIGHTNINGD` for attaching a debugger to each `lightningd` instance created.
45
45
46
+
Alternatively, to run a specific test via the `Makefile`, you can specify the test by setting the environment variable `PYTEST_TESTS`:
47
+
48
+
`PYTEST_TESTS="tests/test_askrene.py::test_layers" make pytest`
49
+
46
50
-**pylightning tests** - will check contrib pylightning for codestyle and run the tests in `contrib/pylightning/tests` afterwards:
47
51
48
52
`make check-python`
@@ -52,14 +56,28 @@ Our Github Actions instance (see `.github/workflows/*.yml`) runs all these for e
52
56
#### Additional Environment Variables
53
57
54
58
```text
55
-
TEST_CHECK_DBSTMTS=[0|1] - When running blackbox tests, this will
56
-
load a plugin that logs all compiled
57
-
and expanded database statements.
58
-
Note: Only SQLite3.
59
-
TEST_DB_PROVIDER=[sqlite3|postgres] - Selects the database to use when running
0 commit comments