Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2021-11-22 | run_single_test: honor the --use-tmpdir flag | Dylan Baker | 1 | -1/+1 | |
2021-11-22 | run_single_test: fix running failing tests | Dylan Baker | 1 | -1/+10 | |
2021-07-07 | Drop checking skippable() in run_single_test | Jon Turney | 1 | -2/+2 | |
Drop checking skippable() in run_single_test. It always returns True unless we are under CI, so checking it here is pointless. | |||||
2021-06-18 | tests: Always enable the traceback in run_project_tests.py | Daniel Mensinger | 1 | -1/+1 | |
2021-06-09 | tests: Reduce complexity of the run_tests signature | Daniel Mensinger | 1 | -24/+12 | |
2021-06-09 | typing: Fully annotate run_project_tests.py | Daniel Mensinger | 1 | -1/+1 | |
2021-03-23 | run_single_test: Handle MESON_SKIP_TEST correctly | Dylan Baker | 1 | -3/+3 | |
2021-02-23 | add a script to run a single test | Dylan Baker | 1 | -0/+89 | |
As a Meson developer it's often frustrating to have a single functional test with a regression. These tests can be awkward to reproduce, especially when they make use of a test.json file. This script provides a simmple interface to call functional tests 1 at a time, regardless of whether they use a test.json or not. If they do use a test.json, and have a matrix, then the `--subtest` option can be used to select spcific combinations, for example: ```sh ./run_single_test.py "test cases/frameworks/15 llvm" --subtest 1 ``` will run only the second (zero indexed of course) subtest from the llvm test cases. This is not a super elegent script, but this is super useful. |