DEV Community

Cover image for Scale with Test Suites: High-performance organization for automated API testing
Preecha
Preecha

Posted on

Scale with Test Suites: High-performance organization for automated API testing

Hey, Apidog users! 👋 Over the past year, we've built a comprehensive automated testing platform around Test Scenarios—reusable workflow sequences that chain multiple API requests into complete business flows. Test Scenarios solve the "how to test" problem, but we've heard consistent feedback from teams about a different challenge: "how to organize what to test."

Try Apidog today

Teams tell us they have hundreds of test cases organized by business modules, but when it's time for release regression, they only want to run their P0 cases—not everything. Currently, they have to manually search and select each one. Others maintain both positive and negative test cases but want smoke tests to only cover positive flows. And when new cases are added, they're often forgotten in regression lists.

Today, we're introducing Test Suites: a new resource type that lets you organize and execute tests by rules rather than by individual selection. Here's how to implement these capabilities in your workflow:

Dynamic Test Routing

Problem: Need to run all P0 cases in the payment module without manual selection.

Solution:

  1. Create a new Test Suite in the Automated Testing module
  2. Select "Dynamic Mode"
  3. Set conditions: Directory = "Payment" AND Priority = P0
  4. Run the suite—all matching cases execute automatically 
// Example: CLI command to trigger suite
apidoq run-suite --suite-id payment_p0 --env production
Enter fullscreen mode Exit fullscreen mode

Image

Key benefits:

  • New test cases matching your conditions auto-include
  • Avoid maintaining static regression lists
  • Works with AI-generated tests

Implementation options:

Mode Configuration Best For
Static Manual case selection Smoke tests (5-15 stable cases)
Dynamic Rule-based inclusion Module regression (changing case counts)

Parallel Execution

Problem: Hour-long serial test runs delay releases.

Solution:

  1. Open suite configuration
  2. Toggle "Parallel Execution" on
  3. System auto-optimizes concurrency
  4. Typical results: 60m → 30m runs

Image

Pro tip: Group dependent steps within a single Test Scenario using sequential requests.

Structured Test Reports

Actionable steps:

  1. Run any test suite
  2. View grouped results by:
    • Module
    • Priority
    • Tags
  3. Failed cases surface automatically
  4. Expand groups for details

Image

# Sample CI/CD integration
apidoq run-suite --suite-id smoke_test --report-format junit > results.xml
Enter fullscreen mode Exit fullscreen mode

Configuration Management

  1. Default behavior: Each scenario uses its saved config
  2. Environment override: Set one env for all scenarios
  3. Full override: Advanced settings for custom configs

Image

Practical Use Cases

Scenario Implementation
Smoke tests Static suite with 5-15 critical cases
Module regression Dynamic suite filtered by directory + priority
Production monitoring Scheduled suite with health check tag

Current Limitations:

  • No suite nesting (but dynamic mode covers most needs)
  • No auto-retry (avoids masking real failures)

Get Started Now

  1. Navigate to Automated Testing → Test Suites
  2. Click "New Test Suite"
  3. Configure using the workflow above
  4. Integrate with CI/CD: 
# GitHub Actions example
- name: Run Regression Suite
  run: apidoq run-suite --suite-id full_regression
Enter fullscreen mode Exit fullscreen mode

Join our community for advanced techniques:

See the Apidog Changelog for latest updates!

Top comments (0)