Contributions
Re: Test Request responses different for TestCase and TestSuite test executions
In the meanwhile, I have again some more information. It seems that my application gives two SOAP responses instead of one, so what happens is the following: 1. First request sent 2. First answer on first request received 3. Second request sent 4. Second answer on first request received AND this answer is regarded as being the answer on the second request => causing the issue. Remark: the answer on the second request is sent by my application but is discarded and does not even reach my PC. This behaviour is seen using SoapUI, and also using JMeter. Does this mean that it is a general problem that can happen on a commercial problem (based on C++ technology), or does this mean that SoapUI as well as JMeter use the same Java library that is not strong enough to detect which SOAP response refers to which SOAP request? Thanks Dominique410Views0likes0CommentsTest Request responses different for TestCase and TestSuite test executions
Good afternoon, My test list consists of some testSuites, in which there are some testCases, most of them containing one testRequest. As such, there are two ways to launch tests: - Individually (Launch either testCase or testRequest) - In serie (Launch testSuite) Now it seems that for some testCases, the received response is different when run individually or in serie, although the application that sends the result behaves in the same way (application traces are identical). ( The http logs that I added previously now seem irrelevant) It seems that the tests in serie are sent in another way than the tests that are sent individually. How can I prevent this and be sure that all tests are executed in the same way? Thanks Dominique1.1KViews0likes1CommentConditional loop
Good morning, I have the following situation: Inside my database there is an object containing an attribute. I have created a SOAP request that can show the full object in a SOAP response. I have another SOAP request that can launch a modify request for the attributes of this object in the database. I would like to do the following: 1. Launch the request that modifies the attributes of the mentioned object and write the current date in the test log. 2. Start a loop, as follows: 2.a) Launch the "show object" SOAP request 2.b) Verify the value that needs to be modified 2.c) If the value is modified, exit the loop and write the current date in the test log. If not, goto 2.a) => It is the intention to know how long it takes (more or less) for the modification to be fully executed. In order to do this, I have created the following: 1. A "Property" test step, containing one property in which I write the value of the attribute. 2. A "show object" SOAP request 3. A "Property Transfer" test step, transferring the result of the mentioned attribute to the "Property" test step. 4. A "Conditional goto" test step. I have following questions: - Verification: The "Conditional goto" test step contains one condition, having: - following XPath expression: //Fraud_counter:text() = 0 - following target step: the "Property" test step. => this doesn't work: I always get this error message: "Error checking condition: net.sf.saxon.trans.StaticError: XPath syntax error at char 24 on line 2 in { //Fraud_counter:text() = 0}: Prefix Fraud_counter has not been declared" - Looping: - I expect from a "Conditional goto" the possibility to go to one place in case of "true" and to another place in case of "false" (so I can return to the SOAP request in case of "false" and go to a last groovy script writing the date in the test log in case of "true") => how do I configure these places to go to? Can anybody help me? Thanks Dominique1.9KViews0likes1CommentRe: SoapUI Pro TRIAL - how to continue DataSource entries when relaunching Test Step
Hello, I believe I have understood the current behaviour of Datasource and DataGen: - When I use a Datasource containing different entries, all of them are read and when I launch the Test Case, the SOAP request test step is launched different times, each time having another value in the DataSource being filled in. - When I use a DataGen containing different, one of them is read (randomly or always the first entry). => I would like the DataGen to use a different value each time I launch the test case. Can anybody help me to do this? Thanks Dominique753Views0likes0CommentsSoapUI Pro TRIAL - how to continue DataSource entries when relaunching Test Step
Hello, I am trying to do the following: - A datasource test step reads the data from a grid (with multiple rows). - A datasource loop links the mentioned datasource with a SOAP request. - I launch the request one time, and when it's finished, I launch it a next time (no load test). => I expect that SoapUI first fills in the first value in the request and the next time fills in the second value (the value in the next row). However, every time I relaunch the SOAP request, the same value is filled in in the request. I have also tried this using a "DataGen" but this gives exactly the same behaviour. Can anybody help? Thanks Dominique1.8KViews0likes2CommentsTransfer stops on "Missing match for Target XPath"
Good afternoon, I have created a property transfer that fills in some properties where needed (at least that's what I want to do. ). My test case now looks at follows: - a property transfer for setting values - some SOAP requests - a property transfer for unsetting values Now I have following problem: the property transfer (which is general for the whole test suite) tries to fill in values on tags that are not necessarily present, and in that case, I would like the property transfer to do nothing and go on. However, the property transfer stops, saying "Missing match for Target XPath". I have checked/unchecked the checkbox "Ignore empty/missing values" but this doesn't help. Does anybody know how I can force the property transfer to continue even if a mentioned tag is not present? Thanks Dominique2.4KViews0likes1CommentRe: newbie: properties don't work + how to use Groovy scripts?
Hello, I have just found part of the solution: - I add a property to my testsuite (%%REF_ID%%=265). - just before each test step, I add a "property transfer", transferring the test suite property %%REF_ID%% towards the test step containing the SOAP request, and as location, I specify "//ref_id". The problem that I have now is that within my SOAP request, the value %%REF_ID%% has been replaced by 265, which means that I cannot use another value for %%REF_ID%% anymore. Does anybody have any idea? Thanks Dominique1KViews0likes0Comments