[GRADLE-2465] Use Gradle's HTML test report for TestNG Created: 06/Sep/12 Updated: 01/Jun/13 Resolved: 27/Dec/12 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | 1.4-rc-1 |
Type: | Improvement | ||
Reporter: | Szczepan Faber | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 1 |
Attachments: | gradle_logging.zip |
Description |
Comments |
Comment by Szczepan Faber [ 06/Sep/12 ] |
Possibly related: |
Comment by Eric Hansen [ 03/Oct/12 ] |
In terms of improving the testng test report, I'd also like support for projects that use both testng and junit. Ideally all *unit test results would be in one report, but it could work with distinct reports as long as they don't overwrite each other. Following instructions from the cookbook results in the {testReportDir}/index.html being overwritten unless a distinct {testReportDir} is set for the testng task. (the Gradle suite/index.html is always available) I'm interested in helping, please let me know how. |
Comment by Szczepan Faber [ 04/Oct/12 ] |
Hey Eric, Thanks for your feedback Here are potential way you can help:
Cheers! |
Comment by Marek Gerhart [ 02/Apr/13 ] |
Is the 1) also resolved? |
Comment by Szczepan Faber [ 04/Apr/13 ] |
Hey can you prepare a sample project that reproduces the problem and attach it to this ticket? Thanks! |
Comment by Marek Gerhart [ 14/Apr/13 ] |
Hi, I attached gradle_logging.zip which contains 2 equal projects - one of them uses testng and the other one uses junit. If you run "gradle test" in both of them and check the reports, only junit also contains logging output in it. |
Comment by Marek Gerhart [ 01/Jun/13 ] |
Can you please confirm that this is an issue and not my misconfiguration? |