> pike -x test_pike is a bundled tool for running testsuites (aka unit tests). > I’m pretty sure the test_pike.pike script described in the link is > essentially the same thing. I use it primarily in my standalone modules[1], > but it certainly isn’t limited to that. I think you also need to use > mktestsuite (primarily to expand the m4 macros (test_any and friends) to > generate testsuite files compatible with the test runner. I have some notes > about writing test suites[2] that expands on the stuff in the manual. > > On a semi-related note, there are some messages in the archives about > assertions and some code that others (Per?) had put together to perform them. > > Hope this helps! > > Bill > > [1] > https://hg.sr.ht/~hww3/pike_modules-public_parser_xml2/browse/testsuite.in?rev=tip > > <https://hg.sr.ht/~hww3/pike_modules-public_parser_xml2/browse/testsuite.in?rev=tip> > [2] http://wiki.gotpike.org/PikeDevel%2FWriting%20Testsuites > <http://wiki.gotpike.org/PikeDevel%2FWriting%20Testsuites> > [3] > http://www.gotpike.org/pikemlarchives/search.pike?query=assert+boilerplate&max=25 > > <http://www.gotpike.org/pikemlarchives/search.pike?query=assert+boilerplate&max=25>
Got the missing bits from the wiki, basically : testsuite.in -> mktestsuite -> testsuite -> pike -x test_pike Thank you ! As a side note, maybe the brew Pike formula could be enhanced to provide mktestsuite in the PATH ? If some kind of interest, here’s an example of a CI that will run the testsuite for a Pike module against latest Pike 7.8 and 8.0 Docker images upon a push on the GitHub repo : https://github.com/bertrand-lupart/pike-public-standards-csv/blob/master/.github/workflows/test-module.yml
