[
https://issues.apache.org/jira/browse/QPID-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003633#comment-13003633
]
Rajith Attapattu commented on QPID-3125:
----------------------------------------
I'd agree with Robbie. I would also prefer a separate target for report
generation. I also prefer the current report format where I can see at a glance
the failures, rather than having to go into each module.
> Add junitreport task for readability in Java unit tests
> -------------------------------------------------------
>
> Key: QPID-3125
> URL: https://issues.apache.org/jira/browse/QPID-3125
> Project: Qpid
> Issue Type: Improvement
> Components: Java Tests
> Affects Versions: 0.11
> Environment: All platforms. Area of functionality is Java based unit
> tests.
> Reporter: Weston M. Price
> Priority: Trivial
> Fix For: 0.11
>
> Attachments: module.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Currently when running the unit tests there is no real convenient way to see
> what has failed and why. The attached patch makes a modification to the
> module.xml file for the java tests to allow junit to print a report after the
> testsuite is run to output the results in html format. The results are placed
> into
> build/results/<module-name>/report/html
> where module name is one of client, common, systests etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
