Thank you for the tip, I sometimes wondered how to make Parenscript tests more friendly for automated testing. I pushed a patch to the repository that exports ps-test:parenscript-tests as an eos test suite, but I don't know when I will make the next release for Quicklisp.
Vladimir On Sun, Mar 11, 2012 at 3:40 PM, Anton Vodonosov <[email protected]> wrote: > Hello. > > The parenscript version in the previous quicklisp had 2 test suites: > > (def-suite output-tests) > (def-suite package-system-tests) > > Current version defines 3 test suites: > > (def-suite output-tests) > (def-suite package-system-tests) > (def-suite eval-tests) > > I suggest to define one top-level test suite, which will include all the test > suites: > > (def-suite parenscript-tests) > (def-suite output-tests :in parenscript-tests) > (def-suite package-system-tests :in parenscript-tests) > (def-suite eval-tests :in parenscript-tests) > > It will help those how can not use ps-test::run-tests function. > > For example in the cl-test-grid project I wan to have detailed test results - > all the failed > tests. Therefore I use eos:run directly. > > Best regards, > - Anton > > _______________________________________________ > parenscript-devel mailing list > [email protected] > http://lists.common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel _______________________________________________ parenscript-devel mailing list [email protected] http://lists.common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel
