Josh Steadmon <steadmon@xxxxxxxxxx> writes: > For various reasons (see discussion at [1]) we would like an alternative > to `prove` for running test suites (including the unit tests) on > Windows. > > This series extends the existing `test-tool run-command testsuite` to > support running unit tests. In addition, it includes some small > cleanups: we move t-basic out of the unit-tests directory, and add a > test wrapper script to allow unit tests and the shell test suite to run > in a single `prove` process. > > Some known remaining bits of work: > * We need to filter out cmake *.pdb files when running with `test-tool`. ;-) I should have read this before I commented on that "--require is misnamed---what you really want is a custom filter" thing. > * We should investigate switching the Windows CI to use `test-tool` > instead of prove. OK. > * We should determine whether it is confusing or otherwise harmful to > people's workflow to have the unit tests run in parallel with shell > tests when using prove as the default test target. It is probably confusing especially given that the testsuite() thing does its own parallel spawning of tests while prove does its own. Is there a reason to choose unit-tests-test-tool Makefile target on prove-capable platforms (other than for testing the test-tool)? Thanks for an entertaining read.
