From: Janne H. <ja...@hy...> - 2004-12-22 17:35:18
|
> If enough people like the idea, I can just commit it, > then we can all change it as needed. > > Clearly, to add extra management: statistics, options to > stop on error or not, or whatever, will require changes. > It doesn't generate native code either. Yep. >>4. Filtering of test cases. Could you make a command line option for >>specifying what tests are included in the test? > > > As an argument to the build of the mainline, > or an argument to the mainline? Or both? By mainline do you mean "mktest"? I mean adding the option to the mktest, not the actual test executable. The reason I want to select tests is a) faster compiles and b) faster execution of tests. This is useful for developing the test suite and for debugging test cases. > The code I posted was mainly intended to be a demo of > the idea. Yes, but it is definitely close to what we want. So for the next steps: 1. Building in tmp directory (extlib-test/build-tmp). This means copying all the necessary source to build dir. This includes tester entrypoint and any additional utility modules (just util.ml currently). I suggested making a library out of the test modules, but I don't think it's such a good idea anymore. Let's make it more simple and just copy the files. 2. Remove the .tst extension and just use .ml. I think we can skip file patching for now.. This is something we can add later. * * John, it would be nice if you could finish the above two steps before committing your test harness generator. Do you have the time to do this? Everything after that can be added more or less incrementally. ciao, janne |