The TestSuite generated by a SuiteBuilder will produce Ant XML results that only has a single suite defined.
At first I figured that SuiteBuilder should be changed to produce a TestSuite per package and per class in order to produce Ant XML results that could be transformed correctly by JUnitReport but now I'm thinking that perhaps the Ant JUnit task should be patched instead.
Does the generated TestSuite currently have enough information to produce XML that would contain info about which package and which TestCase each test method belongs to?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
JUnitReport is XSLT based so without looking into the details, I'm assuming that it's just looking for <testsuite> tags in the generated XML results.
I'm pretty sure batchtest creates a separate suite for every package and class. The only bad thing is that it runs each one in a separate process which makes it significantly slower.
I just took a look at the SuiteBuilder code on the weekend and I agree that it probably won't be too difficult to do this. If you don't have time, I can take a look at this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It would be best if you can take a look at it (and this will be much appreciated). For the following reasons:
- this project is a collaborative work so if someone needs a feature, he has to develop it (and not just ask for it)
- the feature will be better coded/tested if the person in charge is using the feature (and has a real interest in it)
- if someone survives the first step of setting up cvs, downloading and compiling the code, he's more likely to collaborate in the future (what I want).
I think that creating a suite per package is a very good idea, with absolutely no drawback. I'll be glad to commit your patch when you submit it.
Thanks for the help
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ack! Just confirmed that Ant is still producing the "wrong" XML (i.e., only one testsuite) even if I have a TestSuite per package. IDEA picks up on this though so it has some value... but it looks like I'll need to patch the Ant JUnit XML format and possibly JUnitReport as well...
Still experimenting but I'd like to post the patch by this weekend.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The TestSuite generated by a SuiteBuilder will produce Ant XML results that only has a single suite defined.
At first I figured that SuiteBuilder should be changed to produce a TestSuite per package and per class in order to produce Ant XML results that could be transformed correctly by JUnitReport but now I'm thinking that perhaps the Ant JUnit task should be patched instead.
Does the generated TestSuite currently have enough information to produce XML that would contain info about which package and which TestCase each test method belongs to?
The SuiteBuilder returns one single suite that contains all previoulsy grabbed TestCases. So I guess that both JUnit-addons and Ant are right.
It could be certainly nice (and not too complicated) to sort the TestCases per package in the SuiteBuilder classes.
Can you have some more infos about how JUnitReport works and how the suite are created when the batchtest is used?
JUnitReport is XSLT based so without looking into the details, I'm assuming that it's just looking for <testsuite> tags in the generated XML results.
I'm pretty sure batchtest creates a separate suite for every package and class. The only bad thing is that it runs each one in a separate process which makes it significantly slower.
I just took a look at the SuiteBuilder code on the weekend and I agree that it probably won't be too difficult to do this. If you don't have time, I can take a look at this.
It would be best if you can take a look at it (and this will be much appreciated). For the following reasons:
- this project is a collaborative work so if someone needs a feature, he has to develop it (and not just ask for it)
- the feature will be better coded/tested if the person in charge is using the feature (and has a real interest in it)
- if someone survives the first step of setting up cvs, downloading and compiling the code, he's more likely to collaborate in the future (what I want).
I think that creating a suite per package is a very good idea, with absolutely no drawback. I'll be glad to commit your patch when you submit it.
Thanks for the help
Ack! Just confirmed that Ant is still producing the "wrong" XML (i.e., only one testsuite) even if I have a TestSuite per package. IDEA picks up on this though so it has some value... but it looks like I'll need to patch the Ant JUnit XML format and possibly JUnitReport as well...
Still experimenting but I'd like to post the patch by this weekend.