Which formatter do you mean? JUnit? there are just three - xml, brief and plain... or a
custom one.
We need for every test the DEBUG messages - this lead to bigger TEST-testname.xml files -
this leads to a huge (unparseable by XSLT) TESTS-Testsuites.xml file.
What do you think about this:
Let's generate TEST-testname.xml files like before, with all the DEBUG messages
Let's parse 817 TEST-testname.xml files (the whole testsuite) to 817 small
TEST-testname_short_version.xml files, just for the purpose to create this two summaries.
Now we could generate two TESTS-Testsuites.xml files, the big one for the html report
(which does not nead a XSL Transformation) and the small one for these summaries where
XSLT is involved.
Pros: We can leave DEBUG messages in the html report
Cons:
- we need a lot of more space ~ 200MB per testsuite
- it could take a while (how long? no idea...) to parse 817 files to 817 smaller files
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4007056#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...