ReAPI Testing Platform Architecture

A QA-First Approach to API Testing

Unlike traditional debugging tools that merely chain API requests together, ReAPI’s testing platform is built from the ground up for structured test automation. It starts with test cases, where each case defines a clear testing objective—ranging from simple API calls to complex workflows—powered by specialized test nodes like API nodes, logic nodes, and context nodes. This architecture ensures test coverage that aligns with a QA mindset, making it scalable, reusable, and automation-ready.

Test Cases & Test Runners

In ReAPI, test cases are the foundation of the testing process. Instead of executing APIs ad hoc, you design structured test cases, which can be:

• Simple: A single API request with assertions
• Complex: A fully automated test flow using decision logic, loops, and context variables

Each test case can be executed individually to verify its behavior. However, when you need to run multiple test cases together, test runners serve as selectors that allow you to define a subset of test cases based on feature, priority, tags, or folders. For example, you can create a User Tests runner to execute all test cases related to user authentication, profiles, and permissions.

Test Deployment: Automating Your Tests

Once a test runner executes successfully, you can automate it using test deployments, which bind a test runner to a specific environment. Example setups:

• User Tests – Production (Bound to the production environment)
• User Tests – Staging (Bound to staging variables)

Each deployment seals a snapshot of the test configuration, ensuring consistent execution across multiple runs.

Multi-Mode Test Execution

Once a test deployment is created, you have multiple options for automation:

Local Execution via CLI

• Download the test deployment
• Run it using ReAPI CLI
• Generate JSON test reports for further analysis
• Upload reports to ReAPI’s web app for detailed debugging

Automated Fetching and Reporting via URI

• Generate a unique URI for the test deployment
• Use ReAPI CLI to fetch the latest deployment configuration automatically
• Run tests locally, just as in standard CLI execution
• Upload reports back to the ReAPI platform for analysis
• Configure notifications for test completion

While this method automates fetching and reporting, the execution still happens locally.

Cloud-Based Serverless Execution

• Run tests entirely in the cloud using ReAPI’s cloud scheduler
• Ideal for public APIs (since no private network access is required)
• Automated notifications based on project configurations

Test Case Organization & Scalability

ReAPI provides flexible organization tools to manage test cases efficiently:

• Folders and Tags: Categorize test cases for better management
• Priorities: Ensure critical tests always run first
• Selectors: Dynamically choose test cases for specific test runners

This approach makes test execution adaptable to different testing needs while maintaining scalability.

Extending No-Code with Code: Seamless Dev-QA Collaboration

When QA teams need more customization, ReAPI offers JavaScript support to extend the platform’s capabilities:

• Inline scripting for API hooks
• Custom assertion functions
• Reusable value functions
• Global utilities

Unlike traditional platforms that separate code from UI, ReAPI seamlessly integrates code into the no-code environment. Developers can write minimal JavaScript functions, while QA teams continue managing test cases through an intuitive UI. This allows:

• Minimal developer effort
• Maximum QA control
• Efficient collaboration

Conclusion

ReAPI’s testing platform provides structured, scalable, and automated testing designed for QA and developers alike. Whether testing manually, executing test runners, or automating deployments, ReAPI ensures a streamlined workflow for comprehensive API testing.