SoapUI NG Pro
  • Preface
  • 1. About SoapUI NG Pro
    • 1.1 Introduction to SoapUI NG Pro
    • 1.2 Application Installation Instructions
    • 1.3 License installation instructions
  • 2. Ready API - How to use
    • 2.1 Creation of Project:
    • 2.2 Test Case Creation
    • 2.3 Assertions
      • Assertions - In Nutshell
      • Groovy Request and Response Save
      • Script Assertion
    • 2.4 Data Driven Testing
  • 3. Execution in SoapUI NG Pro
    • 3.1 Running Tests From Test Steps
    • 3.2 Running Tests From Test Suites
    • 3.3 Running Test From Project Level
  • 4. Report Generation in SoapUI NG Pro
    • 4.1 Test case Level
    • 4.2 Test Suite Level
    • 4.3 Project Level
  • 5. Continuous Integration
    • 5.1 Jenkins ReadyAPI - Installation instruction
    • 5.2 CreateTests from Jenkins
    • 5.3 Run Tests from Jenkins
    • 5.4 Resolve License errors in Jenkins
Powered by GitBook
On this page

Was this helpful?

  1. 3. Execution in SoapUI NG Pro

3.1 Running Tests From Test Steps

Previous3. Execution in SoapUI NG ProNext3.2 Running Tests From Test Suites

Last updated 5 years ago

Was this helpful?

When you run tests from the request window, only the selected request is simulated. This is convenient when you prepare for testing or when you run simple tests, since you can instantly access the response, modify the request or add assertions.

In more complex tests the requests often rely on the data from previous TestSteps, these requests will fail. To run the individual request, click play button

When you run tests from TestCases, all TestSteps in this TestCase are simulated in order. The editor provides a wide variety of possible actions that are not available on TestStep level, such as comparing test runs or viewing test history. To run all TestSteps in the TestCase, click play button