SoapUI NG is the functional testing tool, where you work with cases, suites and steps with validating assertions to create complex testing packages to fit a great number of different circumstances and scenarios.


→


Ready! API offers a number of authorization methods for use in your tests.

→

Getting Started With SoapUI NG

Ready! API is a complex tool that supports functional, load and security testing of services, while also providing the ability to create a local virtual copy of the service to run your tests before the service starts.

In this tutorial, we give a brief overview of how to create simple functional tests in SoapUI NG. The sections of this tutorial contain a description of how to create a project in Ready! API, create a simple test from an API definition and assert test results.

→

SOAP Testing

Data-Driven Testing

One of the common testing practice is using different testing data to verify the service works correctly in different circumstances, The easiest way to do it is to use data-driven approach. In this case, test executes the same steps several times with using different set of data. You can obtain the data from the external storages or generate it during the test run.

→



Ready! API provides extensive options for scripting, using either Groovy or JavaScript as its scripting language. The default is Groovy, but this can be changed at the project level in the project details tab.

Scripts can be used at the following places:

  • As part of a TestCase with the Groovy Script TestStep, allowing your tests to perform virtually any desired functionality
  • Before and after running a TestCase or TestSuite for initializing and cleaning up before or after running your tests.
  • When starting/stopping a Virt to initializing or cleaning-up Virt state
  • When opening/closing a Project, for initializing or cleaning-up Project related settings
  • As a dynamic DataSource or DataSink with the corresponding DataSource/DataSink TestSteps
  • For providing dynamic Operation dispatching.
  • For creating dynamic VirtResponse content
  • For creating arbitrary assertions with the Script Assertion
  • To extend SoapUI itself (see Extending SoapUI), for adding arbitrary functionality to the SoapUI core

All scripts have access to a number of situation-specific variables, always including a log object for logging to the Groovy Log and a context object for perform context-specific PropertyExpansions or property handling if applicable. A context-specific variable is always available for directly accessing the SoapUI object model.

Additional Concepts

Help and Feedback

You did not find what you looked for?

© 2016 SmartBear Software

Didn't find an answer? Try searching here: