Skip to main content

Scriptless API Testing

Overview

TestGrid’s Scriptless API Testing feature enables users to configure, execute, and validate API requests directly within the Scriptless automation module — without writing any code. Designed for teams that need to incorporate API-level checks into their end-to-end test flows, this feature allows API requests to be defined once and reused across test cases, with response data extracted and applied dynamically during test execution.

This capability is particularly suited to use cases where API responses need to feed into UI-driven test scenarios — for example, retrieving a value from a backend service and using it as an input or validation point later in a scriptless test case.

Key Capabilities

  • No-code API configuration: Define API requests (GET and POST methods currently supported) through a guided UI, without requiring scripting knowledge.
  • Structured request setup: Configure request name, method, parameters, and headers through dedicated tabs, with configurations scoped to a specific project, version, and test suite.
  • Parameters and Headers support: Both request parameters and request headers can be configured independently, each supporting dynamic values or static (temporary) override values.
  • In-context API testing: Use the “Test API” action to execute the configured request immediately within the modal, populating the Data Preview panel with the live response before saving — no need to save first and validate later.
  • Self-signed certificate support: A “Trust self-signed SSL certificate” option allows requests to be tested and executed against endpoints using self-signed certificates.
  • Response data mapping: Extract specific values from API responses using key path selection, including support for nested objects and array indexing (e.g.,Test_id[1].test_id), with explicit data type assignment (e.g., string, JSON/object) for each extracted key.
  • Reusable request library: Saved API configurations are stored under the “API Requests” section of the relevant project and can be reused across multiple test cases. Existing configurations can be revisited and updated via an “Update Configuration” action.
  • Seamless test case integration: Incorporate configured API calls into scriptless test cases using the “Get From API” action keyword, allowing API data to be used directly within broader test logic.
  • Reusable request library: Saved API configurations are stored under the “API Requests” section of the relevant project and can be reused across multiple test cases. Existing configurations can be revisited and updated via an “Update Configuration” action.
  • Seamless test case integration: Incorporate configured API calls into scriptless test cases using the “Get From API” action keyword, allowing API data to be used directly within broader test logic.
  • Execution visibility: API calls made during test runs are logged within the Scriptless execution logs, providing traceability for request/response behavior alongside other test steps.

How It Works

  1. Configure an API request (name, method, endpoint URL) within the “API Requests” section of a project.
  2. Add request parameters/headers as needed, using dynamic or static values.
  3. Use “Test API” to execute the request and preview the live response in the Data Preview panel.
  4. Select the relevant response key(s) — including nested or array values — and assign each a data type.
  5. Save (or update) the configuration for reuse across test cases.
  6. Reference the saved API request in one or more test cases using the “Get From API” action.
  7. Execute the test case; the API call and its result are recorded in the Scriptless execution logs.

Current Limitations

  • Only GET and POST request methods are supported at this time.

Ideal Use Cases

  • Validating backend API responses as part of a broader UI test flow.
  • Retrieving dynamic data (e.g., IDs, tokens, status values) from an API to drive subsequent scriptless test steps.
  • Teams looking to combine lightweight API validation with UI automation, without maintaining separate API testing scripts.

#Read Data From JSON API Response

Retrieve rates from a CI endpoint and extract a specific nested value (ex. GBP) for use in a test case.

 

 

Tags:
Table of Contents