| .. | ||
| test_arithmetic | ||
| test_array | ||
| test_bool | ||
| test_date | ||
| test_dec/good | ||
| test_default/bad | ||
| test_enum | ||
| test_exception | ||
| test_func | ||
| test_io | ||
| test_literate/good | ||
| test_metadata/good | ||
| test_money | ||
| test_name_resolution/good | ||
| test_proof | ||
| test_scope | ||
| test_struct | ||
| test_typing/bad | ||
| test_variable_state | ||
| Makefile | ||
| README.md | ||
Catala test suite
This folder contains Catala source files designed to test the features of the language.
Tests are declared inside plain Catala files with the following format:
```catala-test-inline
$ catala ARGS
... output from the catala command ...
```
Workflow for adding new tests
- Create a new test file in
foo/{good,bad}/bar.catala_<language>(pick the right directory and an informative name for your test) - Write your test, and pick a toplevel scope
Ato run. - Add the following section to your file:
```catala-test-inline $ catala Interpret -s A ``` - Run
make tests/foo/{good,bad}/bar.catala_<language> CLERK_OPTS=--resetfrom the root of the Catala repository. This will update the test with the actual output of the catala command. - Don't forget to
git addthe test file.
Workflow for fixing regressions
- Run
make test_suitefrom the root of the Catala repository, if a test fails you should see something likeFAILED: foo/{good,bad}/bar.catala_<language>.out]followed by the diff between the expected output and the current output of the command. - Debug the compiler and the test and repeat. Run
make tests/foo/{good,bad}/bar.catala_<language>to check the test again. - When you're finished debugging, if you are positive that a change in the test
output is legitimate, record the new outputs with
make tests/foo/{good,bad}/bar.catala_<language> CLERK_OPTS=--reset. - Re-run
make test_suitefrom the root of the Catala repository to check that everything passes. - Run
git diffto double-check your changes to the test outputs are expected. If necessary, justify them in your commit message.
If a compiler change causes a lot of regressions (error message formatting changes
for instance), you can mass-reset the expected outputs with
make test_suite CLERK_OPTS=--reset.
git diff will then allow to check all the changes at once.
Caution: It's your responsability to check all the changes before committing them.
Tips
-
Running a single test-file just to check changes when tweaking either the compiler or the test file itself, but without updating or diffing with the reference can be useful when debugging. The following command outputs the result to
stdoutand can be used from within text editors:clerk runtest test-file.catala_en # Or, to use the current build artefacts, wrap with `dune exec`: dune exec --display=quiet --no-build -- clerk runtest -e dune -c "exec --display=quiet --no-build -- catala" test-file.catala_en