On Thursday, 30 April 2026 18:31:57 BST Martin Frb via fpc-devel wrote: > Not exactly what I meant... If you do it this way, then you can only > match the entire output against one expectation for it all.
Maybe not 100% what you described, but it sound like it's very similar in concept to my integration tests (not unit tests) I defined for OPDF's cli debugger. https://github.com/graemeg/opdebugger/tree/master/tests/integration Maybe there is something useful you could reuse. * Integration tests are trigger by running the 'run_test.sh' script. * Each test has *.commands as input and *.expected as what it expects. * The test run creates a *.diff file. If that file is not 0 bytes, something broke. Regards, Graeme _______________________________________________ fpc-devel maillist - [email protected] https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
