ReportNG – Simple HTML reporting for TestNG
The default HTML reports generated by TestNG, though comprehensive, are a little bit horrid. Since Cedric introduced a reporting API to TestNG a little while ago, I have been using my own hacked together, Velocity-powered reporter.
It’s very simple and doesn’t have all of the information from the default report but it is easier to work out what’s going on with your test results at a high level. I’ve had it in a Java.net repository for a while and now I’ve just produced a slightly improved version for download by anybody that might find it useful.
- A real-world example (unit tests for the Watchmaker Framework)
- A very simple sample report showing some failures
It’s not particularly slick and there is room for improvement. Suggestions are welcome.
on December 10th, 2007 at 1:31 pm
Hi,
I have imported the reportNG.jar file and started.Everything is fine but while viewing the reports I have a problem.
All the files index.html,overview.html,suites.html are generated but when I click on index.html am seeing some links which are not directing me to overview.html or suites.html.How can I solve this problem?
on December 10th, 2007 at 2:23 pm
Hi Teja, I’m not sure what the problem is. Are you able to show me the generated files (either put them on the web or mail them to me)? My address is dan at this domain.
on March 5th, 2008 at 11:41 am
Hi Dan,
I’m extremely sorry for delayed reply.It’s because of some critical tasks piled up and now I have got time to look into reportNG.
Now that I downloaded your latest version reportNG 0.9.2 and it works fine.Thanks for that.
.,
I’m working on customizing my reports.Will get back to you incase I need any help.
on April 7th, 2008 at 11:37 am
Hi Dan,
Currently the reports does not show if the verified statements are passed.
how do we achieve this?kindly let us know ASAP if you have the solution.
Thanks & Regards,
Teja
on April 7th, 2008 at 1:43 pm
Sorry, it’s not clear what the problem is. I’m not sure what you mean by “verified statements”.
on April 8th, 2008 at 8:41 am
Sorry Dan, here is the clear description of the issue that we face here.
Suggestion 1: It would be more descriptive, if we can show the Expected & Actual “String / Message text”
Example:
java.lang.AssertionError: No. of Verifications failed…1
Message: expected: but was:
Current test reports for a given selenium API call like “verifyElementPresent” or “verifyTextPresent” comes in the report as below
java.lang.AssertionError: No. of Verifications failed…1
Message: expected: but was:
Suggestion 2: These verification statements like verifyText.,etc should be shown in the test reports for better users clarify on the test reports. Currently the report comes for only failed verification. Ideally this should come for both Failed and Passed scenarios.
Regards,
Teja
on April 9th, 2008 at 10:03 pm
I haven’t used Selenium yet, so I’m still not 100% clear. It might help me to see exactly what you want if you can show me the reports that get generated when you run Selenium.
Do you get the kind of output you want when you use the standard TestNG reporter? Do you get it if/when you use JUnit with Selenium?
The message that ReportNG displays is just the String returned by calling getMessage() on the exception (or AssertionError). So we’d need to ensure that the message is formatted as required before it gets to ReportNG.
on April 16th, 2008 at 6:40 am
Hi Dan,
Well said, that was an enhancement that I was suggesting as testNG, JUnit etc., do not have that option
I am moving to another project…reportNG is a wonderful reporting engine…I loved exploring the same. Gr8 work Dan.
ALL THE BEST…
Cheers,
Teja