Tutorial # 2 – Built in tools available in Parasoft SOATest

No comments

SOAtest includes a variety of tools that help you test Web services.

The list of tools and their functions are taken from the Parasoft SOATest documentation.

You can also extend SOAtest’s capabilities by scripting your own tools or integrating third-party tools into the SOAtest environment. 

SOAtest can apply the following tools.

Category Available Tools
Messaging Tools SOAP Client
Messaging Client
Message Stub
REST Client
webMethods
EJB Client
Call Back
UDDI Query
Transmit
ISO 8583
XML Tools XML Validator
XML Data Bank
XML Sort
XML Transformer
XSLT
XML Encryption
XML Signer
XML Signature Verifier
XML Encoder
XML Decoder
Viewing Tools Traffic Viewer
Event Monitor
Edit
Write File
File Stream Writer
stderr
stdout
Validation Tools Diff
WS-I
DB
XML Assertor
WS-BPEL Semantics Validator
Web Application
Tools
Browser Testing
Browser Contents Viewer
Browser Validation
Browser Data Bank
Browser Stub
Scanning
Check Links
Spell
HTML Cleanup
Search
Browse
Other Tools Header Data Bank
JSON Data Bank
Object Data Bank
Coding Standards
FTP Client
External
Aggregate
Extension (Custom Scripting)
Attachment Handler
Decompression
Jtest Tracer Client
WSDL Content Handler
WSDL Semantics Validator

Most test suite test cases are based on a SOAP Client tool and use other tools as “outputs” that operate on the messages that the SOAP Client tool returns. For example, if you  wanted to test if a certain SOAP remote procedural call always returned the same output for a given input, you might create a SOAP Client tool, then use a Diff control as its output. Or, if you wanted to test whether a Web service returned values in a correct format, you might create a SOAP Client tool, then use a Coding Standards output to apply a set of rules that checked if the output matched a certain required pattern. If it did you could attach a regression control to the Coding Standards; SOAtest would then alert you if the Web service failed to match that required pattern in subsequent tests.

Few commonly used tools are explained below.

The Browse tool is used to send the designated file or tool output to a browser. When run, this tool will open a new browser window using the system default browser or another browser of your choosing.

With support for Binary, Text, XML, and JSON, the Diff tool is the current backbone of a best-practices regression testing solution. The Diff tool compares the data in its editor against the data that it receives from another tool’s output or from another input that you specify and reports a failure when it finds a difference.

The Edit tool sends data to SOAtest’s internal Edit. This tool is primarily used in test suites to provide a way to access the files that the File Writer tool creates. It can also be used when you want to view or edit the results of another tool.

Scripting/Extension Tool – The primary tool for interfacing with the Extensibility API. It allows for extending tests with actions that may not be directly supported by built-in features. Supports Java, JavaScript and Python/Jython for writing custom scripts that address unique system needs. This tool permits users to perform complex validation or transformation operations on tool outputs, or execute any custom actions as part of test scenarios.

The Write File tool converts output data to files and is typically added as an output to an existing tool. The file can be named with a number of wildcards that include date, time, test name, and a unique ID.

The XML Assertor is used to enforce the correctness of data in an XML message. It is most commonly connected to a SOAP Client or Messaging Client in order to verify the data returned by a service.

The XML Data Bank can be chained to any SOAtest tool that outputs XML. A common example is a scenario wherein an element from the response of one test is used to populate the value of an element in the request of another test. Data in the XML Data Bank can be sent to a Writable Data Source and accessed in the Extension Tool.

The XML Transformer gives you XSLT-like functionality to transform any XML. This is very useful if you would like to create a regression control using only a few elements of the SOAP response or request. Any time you would like to pass a particular subset of an XML response to a chained tool, the XML Transformer is the tool for the job.

XML Validator  – This tool checks whether XML is well-formed and can also validate XML against schema definitions. It is primarily chained to the response output of a SOAP or Messaging Client.

Please comment below if you like to know more about Parasoft SOATest built-in tools.

 

 

 

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s