Message Content Assertion: Assertion is looking for null fields even though it worked previously
When I run my call I get the following JSON object: { "data": { "id": 159, "zoneName": "NameofZone", "createdAt": "2019-09-11 19:25:31", "updatedAt": "2019-09-11 19:25:31", "groupsId": null }, "status": "success", "code": "200", "message": "Operation success", "version": "2" } I setup a Content Assertion on the response to validate that the fields exist: I can run this call any number of times back to back and the message content assertion will always pass. However, when I run the entire Test Suite and the same step is run the message content assertion will always fail. It will give an error as if it were trying to find null nodes in the response (shown below) Any idea or insight into why this is happening? Is there any way to prevent this? Currently I am removing the contract assertion from the test case but that kind of defeats the purpose of the test.Solved3.3KViews0likes12CommentsWhen doing an assert on a large response (10,000-50,000 lines) SoapUI is taking a long time 5+mins.
I have a response that is anywhere between 10,000 and 50,000 lines. I have a few asserts that check the uniqueness of those values. I understand this will take some time, but is there anyway to designate more resources to SoapUI so that these don't take forever? I've had a 46,000 line that takes almost 15min to process one assert! I am on the latest release of SoapUI. I've also played with the testrunner.bat and ready-api.bat filesandun-remmed the line and upped the value for: set READY_XMX=16000m along with Xms512m Appreciate any help in this matter!Solved2.9KViews0likes9CommentsCopy assertion
Dear community members, I would like to know how can I copy assertions from 1 test case to another, such that the referred expected values are also updated accordingly. Here is my scenario: Test Case 1: contains DataSet1, RestRequest1, Assertion1 Test Case 2: contains DataSet2, RestRequest2 .... and so on... upto Test Case 60: contains DataSet60, RestRequest60 The Assertion1 (of test case 1) is a Message content assertion and its expected value is referred as ${DataSet1#out_value}. My intention is to copy assertion1 to the other 59 test cases. But when I copy assertion 1 to TestCase n, the copied assertion is still referring to ${DataSet1#out_value}. And then I have to manually modify each copied assertion to DataSet n. Is there a mechanism where when I copy assertion to testCase n, it automatically refers to ${DataSet n#out_value}. Thanks in advance.1.3KViews0likes3CommentsAssertion Test step gets False Failure
Hi, I am new to SoapUi and ran into some troubles for which I could not find an answer in already discussed topics. It may sound stupid, but here it goes. I have a test case with a Datasource, a request, an assertion step, DataSink and DataSourceLoop. The Request has a couple of assertions - Http Valid Codes (200) and a script assertion with below script: import groovy.json.JsonSlurper def response = messageExchange.response.responseContent def slurper = new JsonSlurper() def json = slurper.parseText response assert json.items.size > 0 Same assertions are added in the assertion script as well. Now the issue is: assertion added in request holds valid when the script is run. However, when the test case is run, the assertions in Assertion test case fail with errors: Status Code extraction failed Cannot read property responsecontent from null object I fail to understand why the same assertion is working when applied in the script but fails when added in the test case. Any leads on the issue would be of great help. Thanks!1.2KViews0likes1CommentCan I change my assertion 'contains' value based on a value in my data source?
I have a datasource. This datasource wouild have a number of rows each representing a different test. Certain values should drive a result of say, true/false I planned on using the datasource loop to loop through my data so I didn't have to build 100 requests. Can my assertion 'contains' be driven from the request data (coming from the datasource). Req1 should have a result of true req2 should have a result of false etc. EDIT: I tried adding a property to my datasource 'resStatus' in my example and using the reference :${DataSource#resStatus} but it doesn't resolve See screenshotSolved1.4KViews0likes1Comment