Forum Discussion
alibaba82
18 years agoSuper Contributor
Hello Ole,
I would like to add on to what Li has said. I think there is a fairly simple and easy way to accomplish this. soapUI already has the option 'launch testrunner' to 'export all results'. The problem with this is that there are way too many files to sort through. It would be better if you can create the folder structure and put the results in the respective folders instead of dumping all results in one folder. So if a project has TestSuite1 (with Testcase A,B,C) and the root folder is C:\results
The export should create a folder 'Testsuite1' with subfolder testcase A,B,C. This way all the result are logically organized just like in the project. If testcaseA has some datasource loop then TestcaseA should have subfolder Iteration1, Iteration2...
Also there should be an option for discarding property transfers etc during export. We are just interested in the request/response.
This feature is important because it lets us keep track of what test were run and what were their results. We can always go back and pull up request/response of previous builds.
For example today I discovered that one of my testcases was failing and this testcase passed in our last release. Development says they have not touched the code and that it should always have been failing. If I have the records I can show developement that the testcase was indeed passing before.
Thanks
Ali
I would like to add on to what Li has said. I think there is a fairly simple and easy way to accomplish this. soapUI already has the option 'launch testrunner' to 'export all results'. The problem with this is that there are way too many files to sort through. It would be better if you can create the folder structure and put the results in the respective folders instead of dumping all results in one folder. So if a project has TestSuite1 (with Testcase A,B,C) and the root folder is C:\results
The export should create a folder 'Testsuite1' with subfolder testcase A,B,C. This way all the result are logically organized just like in the project. If testcaseA has some datasource loop then TestcaseA should have subfolder Iteration1, Iteration2...
Also there should be an option for discarding property transfers etc during export. We are just interested in the request/response.
This feature is important because it lets us keep track of what test were run and what were their results. We can always go back and pull up request/response of previous builds.
For example today I discovered that one of my testcases was failing and this testcase passed in our last release. Development says they have not touched the code and that it should always have been failing. If I have the records I can show developement that the testcase was indeed passing before.
Thanks
Ali