Well, mktestsuite is just a shell script that runs m4. There isn’t anything that’s particularly “compile-time centric about it”. And certainly test_pike could be modified to automatically update the test suite file if needed.
The m4 dependency means that you wouldn’t necessarily be guaranteed to be able to generate testsuites on any machine that merely had pike installed (Windows in particular comes to mind). If you’re distributing code as an archive, you could always generate the testsuite as part of the archive generation process. I use test suites to test some of my own code and while I use makefiles to automate it, there’s no reason it needs to be that way. Making test_pike regenerate the test suite if necessary would make it even more seamless. Even if test_pike weren’t modified to run mktestsuite when necessary, it might be nice if test_pike noticed that a testsuite.in had been modified and made a note of it in the output. Bill > On Sep 7, 2023, at 4:56 PM, Bertrand Lupart <[email protected]> wrote: > > Hello, > > >>> As a side note, maybe the brew Pike formula could be enhanced to >>> provide mktestsuite in the PATH ? >> >> I'm not sure what the best solution is for this; "mktestsuite" is kind of a >> generic name. Maybe we could add an option to test_pike to generate the >> testsuite? > > Getting back some attention about this subject. The process of generating > testsuite files from testsuites.in ones would look like more consistent to me > if invoked from pike -x something > > > However, I understand this testsuite stuff is compile-time-Pike-centric > (makefile and such), and I’m looking for something more run-time'ish, that > would test your own Pike module against a pre-installed Pike interpreter. > > 1- testsuite.in file are distributed alongside own Pike module code > 2- on the system likely to run the module, pike -x something runs the tests > (and probably need to generate/update testsuite files on the fly) > > > Are testsuite suited for that, or should i look elsewhere ? Pest [1] comes to > mind > > > Thank you, > > > Bertrand > > > [1] https://github.com/poppa/pest <https://github.com/poppa/pest> >
