3.1 - Services Workbench

Service Suite documentation.

Service Suite Overview
Why Service Suite?
Netboard Service Usage in Service Suite
Run Node.js Packages from Service Suite
WSDL/SOAP Calls in Service Suite

Service Suite Overview

Recommended guidance

Service Suite is AIQ’s API and service testing area for building HTTP requests, validating responses, extracting values, and supporting API-driven test workflows. Use “Service Suite” in current documentation instead of older Services Workbench wording unless referring to legacy navigation or historical assets.

What Service Suite supports

HTTP API requests with headers, parameters, bodies, and authentication.
Assertions for status codes, response fields, schemas, and business rules.
Response extraction for reuse in later service or Scenario Editor steps.
Data-driven API tests using DPLs or controlled test data.
Evidence through logs, reports, and reusable service assets.

Best practices

Start with small, independent requests before chaining complex workflows.
Use secure credential handling and mask sensitive values in shared evidence.
Document dependencies on external services, rate limits, and environments.
Review older Services Workbench pages for consolidation into Service Suite content.

Last updated: October 6, 2026

Why Service Suite?

Service Suite is used to design, run, and validate API and service-level tests in AIQ. It helps teams test business workflows below the UI, validate integrations, and reuse service calls across broader test coverage.

When Service Suite is a good fit

Testing HTTP APIs, service integrations, and backend workflows.
Validating data contracts, status codes, response payloads, and downstream values.
Creating reusable service steps that support Scenario Editor or end-to-end tests.
Running checks that should be faster or more stable than browser-only validation.
Preparing setup, teardown, or data-creation steps for larger test suites.

Recommended practice

Use Service Suite with clear request definitions, secure authentication handling, assertions, response extraction, and environment-specific variables. Keep service tests small enough to debug quickly, then combine them into broader workflows where needed.

Last updated: October 8, 2026

Netboard Service Usage in Service Suite

Last reviewed: September 25, 2026

Use this article when a Service Suite workflow needs to call or validate the Netboard service.

What changed in this article

Clarified that this is Service Suite integration guidance, not a general product overview.
Added checks for endpoint availability, request payload, authentication context, and expected response shape.
Added troubleshooting details around response validation and output logging.

Validation workflow

Confirm the Netboard endpoint and required request fields.
Run the Service Suite call with a known test payload.
Validate the response body, status, and any downstream values stored for later steps.

Review note: Kept the article but scoped it to Service Suite usage and validation.

Last updated: September 25, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Run Node.js Packages from Service Suite

Service Suite can invoke approved Node.js and npm-based processes on the AIQ execution host. Install Node.js, npm, and required packages on the same Test Node or host that runs the Service Suite test.

Plan for the call to wait until the external process completes. Capture and validate the process exit status, standard output, and standard error in the test logic.

Use a controlled working directory and avoid installing untrusted packages during execution. Validate package compatibility with the deployed AIQ and Node.js versions before use.

Last updated: September 14, 2026

If you have any feedback on this topic, please contact us at documentation@appvance.ai

WSDL/SOAP Calls in Service Suite

Recommended guidance

Use Service Suite for WSDL/SOAP calls when the tested system still exposes SOAP services or when a legacy integration requires SOAP validation. Keep the documentation focused on request structure, endpoint configuration, authentication, assertions, and evidence.

What to configure

WSDL location, SOAP endpoint, operation, namespaces, and request body.
Headers, authentication, certificates, proxy settings, and timeout behavior.
Expected response status, SOAP fault handling, and response assertions.
DPL or environment values used in request payloads.

Validation workflow

Validate the WSDL and operation outside the main regression suite first.
Run a known-good request with controlled data.
Add assertions for both transport success and business response values.
Mask credentials, tokens, and sensitive payload values before sharing evidence.

Last updated: October 7, 2026