I want to understand the difference in running the soap ui test runner.bat from command line or from Test Maker versus running it from within the Soap UI tool.
The reason is, I have script assertions which writes the results to a log file. It creates the log file which I run the test case from within the tool. but when I invoke it from command line or from test maker tool, it does not execute the script assertion and does not produce the file.
I have both SOAP ui non pro version and the pro version with trail license.
I get NoClassDefFoundError while invoking testrunner.bat from cmd line while using no pro version and I get System could not find the path specified while using pro version.
I was reading a tutorial on Soap ui pro where we could create properties on response and create a transfer to transfer the value of the properties from the response to the property. that link also had a data source loop to be created to get the properties for all the requests posted to the service.
I am trying to parse out the response to get some specific values from the response. Initial thought was to save the response a files and to write a java program to parse the response. But for testing maintainability is a bug thing with this approach.
Is this configurable in soap ui pro by using properties and transfers? Is yes, can someone tell me how?
I have this resolved now. I had to change the order if the test steps (I was not aware the order matters)
Now I have the responses saved for all the requests. The idea is to write programs to extract information to have test results compared with expected results.
Thanks for all the information Ole and I will use the groovy site as I will be writing more and more of that.
I have outFile.close() right after I write the response to the file. It is not able to capture the responses.
Instead if I out the same script as a script assertion, it is able to write the response to the file. But the draw back is I get only one file with the last request and response. I need to save all the responses.
I want to try some try catch and finally block to handle to this situation where I can force things a bit. for that, I need some help with Groovy scripting. Can anyone point me to a good source on Groovy where I can see the usage of the scripting language and also some examples?
I am able to save the response into the file. I was able to do this with the assertions as well. I have moved the assertion to a test step now.
But the file comes out empty. Could it be the problem where the file object is still not closed completely and the next request is trying to access the same object?
I have testdata.properties in the format for example name1=data1,data2,data3
I have a properties test step defined reading the data from this properties file for the property name = name1
I also have a data source and data source loop test step to read the data from this properties file and to loop through the data with comma separation between data.
The idea here is to have the datasource read the file and loop through the data from 1 through 3 and feed each one at a time to the properties step.
The request is built to take the data from properties like ${Properties#mesLotName}
I am not sure if this is the right way to set up the steps in this order to achieve data driven testing looping through a set of test data.
But it is not working the way I expect it to. It is reading the datasource but putting the entire line with comma as the property value so the response is NullPointerException where it cannot qualify the data input.
Could someone please let me know what is the best way to fix this scenario or if there an alternative to this?