Selecting a suitable running method#
Apidog provides multiple ways to run test suites, suitable for different testing requirements.This method is initiated from a local machine and is suitable for small-scale, quick testing.
It is particularly effective when development and testing occur simultaneously, allowing for real-time monitoring and immediate adjustments.
Ideal for handling large-scale data or iterative scenarios, this method offers increased execution speed.
It is capable of running offline, which is suitable for environments with restricted resources or those that do not require a graphical user interface.
This execution style is integrated within the CI/CD pipeline, making it a great option for automated integration and continuous deployment processes.
It is especially useful in settings where tests are frequently run to confirm the stability of APIs after each code update.
4.
Self-hosting runner execution:
Teams can set up the Apidog Runner on their own servers, leveraging more robust computing resources for testing.
This method includes support for scheduled tasks, making it ideal for scenarios that need regular testing or those with significant testing demands.
In test suites, if environment/global variables are used, the actual values of these variables may differ depending on the execution method chosen, which could lead to inconsistent test results. Learn more. Execution configuration in test suite#
When running test suites in Apidog, you can configure multiple settings and options to run tests according to specific requirements.General configuration#
You can adjust the following settings in the run configuration on the right side of the test suite:Specify the service (base URL) to which requests in the scenario should be directed and the variable set to be used. For details, see Environment Management. The machine that actually consumes hardware resources to run test suites. All requests initiated in the test suites will be sent from the machine specified here. Therefore, differences in the network environment of the requesting machine may lead to varying test results.This setting will not be saved as part of the test suite's run configuration. Each time, the local machine will be used by default to run the test suites. Additionally, this setting will not take effect during batch runs or CLI executions. In these cases, requests will be initiated using the resources of the current machine.
Enabling this feature will send notifications to specified recipients once the manual test suites is complete. The notification will include an overview of the test results and a link to the detailed report. You can configure whether to send the notification as soon as the test completes or only when a failure occurs, helping to minimize unnecessary alerts. Refer to notification settings for more detailed information. Modified atΒ 2026-01-13 10:04:10
