Hi, we are using APIDOG for our API testing. We have one test where we need to wait for 24 hours, so we used the delay step.
When looking at the results and report, we noticed the test did run, but seemed to have skipped the test steps after the delay. This is confirmed by our server logs, since it clearly shows a 24-hour period between the requests, but no requests related to the steps after the delay. The next log is from the next test in the sequence.
Also in the test report, the duration shows a negative number (see screenshot).
Not sure if we did anything wrong, or are misusing the delay functionality.
Hi DexterLerteco,
Since Apidog isn’t specifically optimized for extremely long-running scenarios, tests with delays as long as 24 hours may encounter skipped steps or report anomalies. The CLI, however, operates independently without such runtime limitations. We recommend running your test via the CLI to ensure full execution of steps with long delays. Check out the docs here: Introduction to Apidog CLI - Apidog Docs.
Thank you for the help!
I am trying the CLI option now, but I am running into some issues with my database operations.
In your documentation it says:
Using database operations in CLI
When your test scenarios include database operations, you need to take a few extra steps because database configurations are saved locally, not in the cloud. This means you can't directly run the CLI in cloud mode for these scenarios. Here's how to handle this situation:
1
For test scenarios that include database operations, you'll see a prompt in the command line generation interface: "Download the database configuration file."
2
Download this file and place it in the directory where you plan to run the Apidog CLI.
3
The automatically generated command line will include the --database-connection option. You can use this command line as is to run your tests.
However, I cannot find this option anywhere to export the configuration file.
I tried an example test with only one step accessing the database, but I get nothing.
I am on version 2.7.7 of APIDOG
I suppose it might just be the normal ‘export’ JSN file? not a special one?