Unlike Postman, Apidog clearly distinguishes between endpoints and debug cases. Each endpoint can have multiple debug cases linked to it. If you update the endpoint’s URL or parameters, all related debug cases are automatically updated — no extra effort needed.In comparison, Postman handles everything as separate, standalone requests. This means if you make a change to a URL or parameter, you’ll need to manually update every affected request one by one.Create an debug case#
When you send a request or debug in the Run tab of an Endpoint, if you want to save the request permanently, you can click on Save as case. This action will preserve the request as an debug case within the endpoint's structure.You can name the debug case and choose whether to save the response simultaneously.What is saved in debug cases#
As mentioned earlier, the endpoint specification is saved within the endpoint, while the values are stored in the debug case. Specifically, an debug case includes the following data:Request parameter values, covering path parameters, query parameters, header parameters, and body parameters in form-data format.
Body content in formats like RAW, JSON, XML, etc.
Pre and post-request processors.
Received response details.
Response validation settings, indicating whether validation is enabled and specifying which response to validate against.
Reference debug case as an automated test step#
Debug cases can be referenced as test steps in automated test scenarios. When referenced, the request parameters in the debug case will be applied directly to the test step. You can see a clear notification that any changes made to the debug case will automatically update all test steps that reference it.Click the referencing icon at the top-right corner to view which test scenarios reference the debug case and the total number of test scenarios that use it. This gives you an overview of how it is used in automated test.Clicking a test scenario takes you to the scenario detail page, where related steps using the case are highlighted for easy viewing.Clicking a test step that references the debug case will notify you that any changes will sync with the original case.Best practices for using debug cases#
1.
Define API specifications thoroughly.
2.
Create multiple debug cases for each endpoint to cover different conditions.
3.
For each debug case, write assertions or other pre and post-request processors.
4.
Reference debug cases in automated tests to compose test scenarios.
5.
If there are updates to the API specifications, both the debug cases and test scenarios can be synchronized. You can choose to update test scenarios manually or set them to update automatically.
Modified at 2025-09-17 06:10:38
