Forum Discussion

Wave_Crest_Hold's avatar
Wave_Crest_Hold
Contributor
14 years ago

Error in processing parameterized values from Excel file

Hi,

I am using SOAP UI Pro 3.6.2 version. I observed below error while parameterize my input data using source as an Excel (.xls) file.

[SOAP Response] error: </body> does not close tag <HR>.
[SOAP Response] </body> does not close tag <HR>.
[XPath Match] XPathContains assertion failed for path [declare namespace ns1='urn:OutgoingTransaction';
//ns1:outgoingTransactionResponse[1]/outgoingTransactionReturn[1]/actionCode[1]] : NullPointerException:null


I checked that the body tag was closed properly.

The same API processed the request if send hardcoded input values in the request instead of parameterized.

Note:
1. I have used .xls file only
2. Closed the file while executing the test
3. Send all the mandatory input fields in the request


Please have a look this issue and provide me the solutions.

Attached screenshot for reference.

Thanks in adv.

3 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    14 years ago
    Hi,

    hmm.. do you have any errors in the error log tab at the bottom of the soapUI Window when this happens? Also, please attach the screenshot, it was missing..

    Thanks,

    /Ole
    SmartBear Stockholm
  • Wave_Crest_Hold's avatar
    Wave_Crest_Hold
    Contributor
    14 years ago
    Thanks for the Reply, Ole.

    Please find the attachment to this reply <<SOAPUI_Issue.png>>.

    I was having a request xml and team was manually typing values in it and calling the service for individual test execution.

    Now i am trying to automate my test cases by parameterizing the values and feeding them from Excel data source. The data is populating and feeding to the request xml properly. Here i observed a change request xml:

    In the request xml that the team was executing the tests, the field was <msgType xsi:type="xsd:int">100</msgType> .
    After i parameterize the input data and call the service, i observed the same field as <msgType xsi:type="xsd:int" xs:type="type:int">100</msgType>. xs:type="type:int" is added to the "msgType" node and similarly to all other nodes. Please find the other attachment for your reference<<Observation_In_Request.png>>.

    Please consider this as high priority, I am blocked because of this issue. Please get back to me if required any further info.

    Thanks in adv,
    Sudhakar Reddy
    +91 9866405405
  • Wave_Crest_Hold's avatar
    Wave_Crest_Hold
    Contributor
    14 years ago
    Hi Ole,

    I found the reason for the issue. One of the parameters which i am sending in request xml is more than the specified length and which was causing this issue. Now my automation task is going smooth. Please ignore my query.

    Regards,
    Sudhakar Reddy
    +91 9866405405