Er, question first, shall we? I wonder if you have a recommendation for how to approach the problem I'm trying to solve, given PerlUnit's current architecture. I want to be able to start a TestRunner running against a dynamically generated suite, where the suite itself is determined by the command line.
So, for instance, I imagine the command line looking something like this: perl TestRunner.pl MyTestMaker arg1 arg2.... where MyTestMaker has a suite() method that uses the arguments to generate the appropriate test suite. The thing is, there's no way for MyTestMaker to get access to the arguments, because they're all eaten up by TestRunner and not passed along. Is there another way (a "right" way) to do this? My solution so far is to bypass TestRunner.pl, instead using a script that generates the test suite, creates a new TestRunner object and starts it running with the constructed suite. The two things I don't like about this are that it relies on the TestRunner::do_run() method, which I'm not sure is a public part of the API, and that I'd rather use TestRunner.pl if at all possible. Any suggestions? OK, now my own small suggestion. I was confused at first when a Boolean assertion failed with the message "Expected TRUE, got FALSE." Seems to me that a Boolean test doesn't have an expected value the way an equality assertion does; how about changing the message to "Assertion failed"? -- Matthias _______________________________________________ Perlunit-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/perlunit-devel
