Idris2/tests
2023-09-07 14:57:22 +01:00
..
allbackends Add testing utilities script 2023-09-07 14:57:22 +01:00
allschemes Add testing utilities script 2023-09-07 14:57:22 +01:00
base Add testing utilities script 2023-09-07 14:57:22 +01:00
chez Add testing utilities script 2023-09-07 14:57:22 +01:00
codegen Add testing utilities script 2023-09-07 14:57:22 +01:00
contrib Add testing utilities script 2023-09-07 14:57:22 +01:00
gambit/bitops001 Add testing utilities script 2023-09-07 14:57:22 +01:00
ideMode Add testing utilities script 2023-09-07 14:57:22 +01:00
idris2 Add testing utilities script 2023-09-07 14:57:22 +01:00
node Add testing utilities script 2023-09-07 14:57:22 +01:00
prelude Add testing utilities script 2023-09-07 14:57:22 +01:00
racket Add testing utilities script 2023-09-07 14:57:22 +01:00
refc Add testing utilities script 2023-09-07 14:57:22 +01:00
templates Add testing utilities script 2023-09-07 14:57:22 +01:00
ttimp Add testing utilities script 2023-09-07 14:57:22 +01:00
typedd-book Add testing utilities script 2023-09-07 14:57:22 +01:00
vmcode/basic001 Add testing utilities script 2023-09-07 14:57:22 +01:00
Main.idr [ new ] function options for case blocks (#3062) 2023-09-01 11:35:52 +01:00
Makefile [ repl ] Add the ability to get detailed help, e.g. :help :help (#2722) 2022-10-21 14:35:33 +02:00
README.md [ re #2649 ] Describe test naming pattern 2022-11-11 09:33:09 +01:00
tests.ipkg Set PREFIX for tests 2021-04-19 11:23:58 +01:00
testutils.sh Add testing utilities script 2023-09-07 14:57:22 +01:00

Tests

Note: The commands listed in this section should be run from the repository's root folder.

Run all tests: make test

To run only a subset of the tests use: make test only=NAME. NAME is matched against the path to each test case.

Examples:

  • make test only=chez will run all Chez Scheme tests.
  • make test only=ttimp/basic will run all basic tests for TTImp.
  • make test only=idris2/basic001 will run a specific test.

Templates for common test instances can be found in the templates folder.

There is no defined naming convention for adding tests, but the pattern has been:

  • a sub-directory in the relevant test section (idris2, refc, etc.)
  • with a descriptive name followed by a 3-digit number (e.g. envflags001 is the first test checking the environment flags functions)
  • containing:
    • an Idris file importing the relevant modules and containing the test function(s)
    • a run file which is a shell script that runs the test (see the existing tests for examples for this)
    • an expected file containing the expected output