WIP: Convert C tests to pytest #1538
Conversation
| cwd=tmp_path, | ||
| ) | ||
|
|
||
| # For files using a config file, copy the config file to the temporary directory. |
There was a problem hiding this comment.
This seems a bit hacky and it might be possible to just run the test with the CWD set to the tests directory so it can find the config json file. I did notice that test/c/config_abstract_type2.sail loads the "wrong" config file, not sure if that is intentional?
There was a problem hiding this comment.
I think they should all use a config file with the same name as the test, so likely a mistake
Test Results 16 files 36 suites 0s ⏱️ Results for commit ea98275. |
|
The only reason we use JUnit XML output is because that's what our old Jenkins server used, if there's something that works better with GitHub and supported by pytest, we could just use that instead. |
|
I think if we stick with Python and are adding third party dependencies we need a |
3 participants
Allows filtering with
pytest -k <filter>and parallel execution with pytest-xdist (pytest -n <jobs>/auto. JUnit xml output is also supported natively.Not ported all the tests yet (lem/ocaml/interpreter) is missing.
Note: I used this to see how well this can be done with AI. Needed quite a few prompts but most of this was generated by Gemini with a few small manual edits.
See #1526