- SoapUI Tutorial
- SoapUI - Home
- Soap Basics
- SOAP - Introduction
- SOAP - Messages
- SOAP - What is REST?
- SoapUI Basics
- SoapUI - Introduction
- SoapUI - Capabilities
- SoapUI - NG Pro
- SoapUI - Installation & Configuration
- SoapUI - WSDL
- SoapUI - Project
- SoapUI - TestSuite
- SoapUI - TestCase
- SoapUI - TestStep
- SoapUI - Request & Response
- SoapUI - Properties
- SoapUI - Property Transfer
- SoapUI - Logs Pane
- SoapUI - Assertions
- SoapUI - Troubleshooting
- SoapUI - Performance Testing
- SoapUI - Load Testing
- SoapUI - RESTful Web Services
- SoapUI - JDBC Connection
- SoapUI - JDBC Property
- SoapUI - JDBC Assertion
- SoapUI Useful Resources
- SoapUI - Quick Guide
- SoapUI - Useful Resources
- SoapUI - Discussion
- Selected Reading
- UPSC IAS Exams Notes
- Developer's Best Practices
- Questions and Answers
- Effective Resume Writing
- HR Interview Questions
- Computer Glossary
- Who is Who
SoapUI - Troubleshooting
In SoapUI, the users face many generic common issues that could be sort out with a little alertness. Some of these most common issues are the following −
Issue − Namespace is defined wrongly. Use the correct namespace. The namespace should be the URL where the web service is located.
Solution − If an error is thrown while developing a scripting assertion, use 'log.info' to print the contents of the variables.
Issue − If a fault-code is received as response XML, it may be due to the invalid input.
Solution − Verify the input of request XML.
Example − In the currency converter, if the input of the 'FromCurrency' is '123' which is not existing, the output throws a fault code as 'SOAP-Client' which means that the issue is with the parameter that is being passed from the client side.
Request
Response
Issue − No match in current response when using XPath or XQuery.
Solution −
- Use the correct syntax while defining XPath or XQuery.
- Verify colon is used and not dot while declaring the namespace.
- Ensure that XPath and XQuery are correct.
