Item400: unit test runner should be more magical
Current State: Closed
Released In: 1.0.7
Target Release: patch
Applies To: Engine
for eg, I should be able to run
../bin/TestRunner.pl -clean SlideShowPlugin
, which makes it look for the nearest Suite file
should look for the nearest Suite file (ie the FoswikiSuite
also, I'd like to be able to request it to run just one specific test -
../bin/TestRunner.pl -clean SlideShowPluginTests::test_Simple
Confirmed and regraded to enhancement. This is one of these "if you don't do it, nobody else is going to unless they need the same thing" jobs.
- 08 Mar 2009
Done on trunk. Shall I merge it to the release branch?
- 24 Mar 2009
release branch - sounds good
oh, the cruelty - I can think of another -
../bin/TestRunner.pl -clean SomeTests::verify_NotSoSimple
- 27 Mar 2009
This works for me. The filter is done on the test array that's built, so if you can see it in the output, you can run it.
And I've merged it onto the release branch.
Sven, thanks to close if it fits your needs
- 29 Mar 2009
As Lavr pointed out, it broke the Suite tests, so:
../bin/TestRunner.pl -clean CommentPlugin/CommentPluginSuite.pm
I've fixed that, but now I'm puzzled. What should:
../bin/TestRunner.pl -clean CommentPlugin
do? For now, it finds both
, and run them both. As the Suite one just includes the Tests one, it's a bit silly.
So what I could do is favor the Suite one if one is found.
What I did is:
So in brief, I think I kept compatibility, with enhancing functionnality.
Let me know if you still can think of something that's not done, or if you can find some ways that aren't working.
- 30 Mar 2009
I don't understand the examples. How does
know where to find
I don't want to throw you into confusion, but I could get my head round a package specification relative to test/unit;
Make / synonymous with :: and strip trailing
and you are cooking with gas. I don't perceive any requirement to simplify it further than that.
- 04 Apr 2009
Sorry, hadn't seen your comment before. It knows where to find it by looking for anything that matches TranslatorTests
.* in the test/unit folder, recursively.
Therefore, there is no need to specify the plugin name.
TestRunner.pl WysiwygPlugin/TranslatorTests -- works, and has always worked
The rest was made so that one can copy/paste the output of a test suite that fails to re-run that specific test.
I think I implemented what you were asking for without reading that. Like one say, great minds think alike.
Please, let me know if you see any way to enhance that further, otherwise I'll close it.
- 22 Apr 2009
I like what you've done - thanks!
- 10 May 2009
i recon its magical.
- 08 Aug 2009