Testing

Two sets of unit tests are distributed with Logtalk. One in the tests subdirectory and another in the examples subdirectory. You can run both sets in a POSIX system by typing:

$ cd $LOGTALKUSER/tests
$ logtalk_tester -p <back-end Prolog compiler>
...
$ cd ../examples
$ logtalk_tester -p <back-end Prolog compiler>
...

There are also a few unit tests in the contributions folder:

$ cd $LOGTALKUSER/contributions
$ logtalk_tester -p <back-end Prolog compiler>
...

To identifiers for the supported back-end Prolog compilers can be listed by typing:

$ logtalk_tester -h
...

Logtalk source code can be compiled in three different modes: optimal, normal, and debug. The logtalk_tester accepts an option, -m, to set the mode to be used to run the unit tests. Be aware, however, that running the unit tests in debug mode can take considerably more time compared with the other two modes.

Note that, when running the unit tests using stable Logtalk releases, failed tests usually result from bugs in the backend Prolog compilers or from their lack of compliance with official and de facto standards. The most common issue is non-standard exception handling. These issues can only be fixed by the developers of those Prolog compilers.

Support for automating running the unit tests on Windows is forthcoming.