Forum Discussion
redfish4ktc2
12 years agoSuper Contributor
Hi guys,
nice to see someone ready to contribute to https://github.com/redfish4ktc/maven-so ... ssues/42!!! :-)
Here are some information I have collected
exportAll: this option is not related to junit report. Soapui generates txt files that contains the details of failing steps (request, response, assertions result). When set to true, soapui generates txt files also for successful steps.
This is implemented directly in the test runner and this behaviour is not specific to Maven. See the source code https://github.com/SmartBear/soapui/blo ... .java#L683
About the JunitReportCollector
I discovered yesterday an hidden feature: it is possible to get the detail of a failure in the junit report by setting the "Complete Error Logs" property to true.
See
* viewtopic.php?f=2&t=2313
* viewtopic.php?f=4&t=2448
This is a pro feature in the gui, but you can create an empty soapui settings file, add the property and make it use by the maven plugin. This should work even with the open source version.
The content of the TestStepResult is written directly as this is done when generating the txt files
I did not have time to test this to see what it produces, maybe later this summer
The source code of the junit collector is here: https://github.com/SmartBear/soapui/blo ... .java#L139
It explains that you only get failures details in the report because all the implementation does not consider any success details
* the afterStep method perform some works only on failures. There is no field that stores successes step or tescases
* the afterRun method shows that the report class currently used stores test details only for failures
This is also what it is explain here: http://blog.infostretch.com/customizing-soapui-reports. They did not give all the implementation but if I had time to implement this feature right now, I would look deeply into this post: it show how to display all steps, expecially successful step and all assertions (this seems to be inspired of the way the testrunner deals with result in its afterStep method).
The details of the step are directly sent to the report related to the current testsuite through sysout and syserr methods
Hope this help
djangofan can you share your implementation on github/gist for letting me have a look at it? Thanks
nice to see someone ready to contribute to https://github.com/redfish4ktc/maven-so ... ssues/42!!! :-)
Here are some information I have collected
exportAll: this option is not related to junit report. Soapui generates txt files that contains the details of failing steps (request, response, assertions result). When set to true, soapui generates txt files also for successful steps.
This is implemented directly in the test runner and this behaviour is not specific to Maven. See the source code https://github.com/SmartBear/soapui/blo ... .java#L683
About the JunitReportCollector
I discovered yesterday an hidden feature: it is possible to get the detail of a failure in the junit report by setting the "Complete Error Logs" property to true.
See
* viewtopic.php?f=2&t=2313
* viewtopic.php?f=4&t=2448
This is a pro feature in the gui, but you can create an empty soapui settings file, add the property and make it use by the maven plugin. This should work even with the open source version.
The content of the TestStepResult is written directly as this is done when generating the txt files
I did not have time to test this to see what it produces, maybe later this summer
The source code of the junit collector is here: https://github.com/SmartBear/soapui/blo ... .java#L139
It explains that you only get failures details in the report because all the implementation does not consider any success details
* the afterStep method perform some works only on failures. There is no field that stores successes step or tescases
* the afterRun method shows that the report class currently used stores test details only for failures
This is also what it is explain here: http://blog.infostretch.com/customizing-soapui-reports. They did not give all the implementation but if I had time to implement this feature right now, I would look deeply into this post: it show how to display all steps, expecially successful step and all assertions (this seems to be inspired of the way the testrunner deals with result in its afterStep method).
The details of the step are directly sent to the report related to the current testsuite through sysout and syserr methods
Hope this help
djangofan can you share your implementation on github/gist for letting me have a look at it? Thanks
Related Content
- 3 years ago
- 9 months ago
Recent Discussions
- 23 hours ago