Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KLISTERPATH for tests #238

Merged
merged 1 commit into from
Apr 25, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 38 additions & 0 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -215,3 +215,41 @@ Imports
The ``import`` form will search for modules in the same directory as the
importing module, and in directories listed in the ``KLISTERPATH`` environment
variable, a ``:``-separated list of directories.

Setting ``KLISTERPATH`` is needed for all tests to pass, as some rely on modules
from the ``examples`` directory;

::

$ cabal test

Test suite klister-tests: RUNNING...
All tests
Golden tests
keyword-used-incorrectly: FAIL
...
+Module not found: keyword-test.kl
+Searched in directory at /.../examples/failing-examples
+And on $KLISTERPATH:
...
wrong-keyword: FAIL
...
+Module not found: keyword-test.kl
+Searched in directory at /.../examples/failing-examples
+And on $KLISTERPATH:
...
bound-vs-free: FAIL
...
+Module not found: do.kl
+Searched in directory at /.../examples/failing-examples
+And on $KLISTERPATH:
...

3 out of 132 tests failed
Test suite klister-tests: FAIL

::

$ KLISTERPATH=examples cabal test
...
Test suite klister-tests: PASS
Loading