Troubleshoot Invalid test data error

adventurous_hamster_08190 · June 13, 2025, 4:49pm

I run all of our Apidog tests using the following command line:

apidog run --access-token [REDACTED] -f [folderId] -r html --out-json-failures-separated out.json

(Trying to run the tests using the UI results in an out of heap space error.)

The output is this:

(node:24380) [DEP0044] DeprecationWarning: The util.isArray API is deprecated. Please use Array.isArray() instead.
(Use node --trace-deprecation ... to show where the warning was created)
error: Error: Invalid test data.

We have nearly 6K assertions spread across around 1K tests. Is there an easy way to identify the test(s) that have Invalid test data?

Thanks!

system · June 14, 2025, 12:30am

Hi Joe,

Have you resolved the issue? I verified it locally and it’s working fine.

Can you check your versions with:

node -v && apidog -v

adventurous_hamster_08190 · June 16, 2025, 6:39pm

It still happens. I am using node v22.15.0 and apidog 1.5.15.

I can update apidog–I see that it’s slightly different–but do note that I have been able to successfully run all tests as recently as a week ago without that error.

I believe that we’ve made a change to a test–tests are constantly being created and updated–that has somehow caused the error, but I don’t know which one it is–that’s precisely the issue.

This same kind of error happens if you inadvertently don’t set an environment for a test–the whole test run grinds to a halt and tells you that something failed, but not the crucial information of what failed.

system · June 17, 2025, 2:51am

Hi Joe, Thanks for the feedback. The issue with --out-json-failures-separated not working has been fixed in version 1.5.18. Please update to the latest version.

system · June 17, 2025, 3:06am

The error message you shared is from CLI execution (“apidog run” command). The UI heap space error is a separate issue.
“The output is this:
(node:24380) [DEP0044] DeprecationWarning: The util.isArray API is deprecated. Please use Array.isArray() instead.
(Use node --trace-deprecation ... to show where the warning was created)
error: Error: Invalid test data.”

adventurous_hamster_08190 · June 17, 2025, 2:04pm

The error message you shared is from CLI execution (“apidog run” command). The UI heap space error is a separate issue.

Absolutely true. I mentioned it only to prevent someone from suggesting that I use the UI to run all the tests because that fails because of the heap space error.

The issue with --out-json-failures-separated not working has been fixed in version 1.5.18. Please update to the latest version.

This is greatly appreciated, but unfortunately if the test run terminates abnormally the output isn’t available.

Current status:

I updated Apidog to 2.7.17 and apidog-cli to 1.5.18 and re-ran.

I still get the “error: Error: Invalid test data.” (I believe that the previous lines, from node, are related only to deprecated packages referenced by the apidog-cli application and can safely be ignored.)

Additional diagnostic/error messages would help me to fix whatever underlying issue exists–or to better describe it for a defect report.

system · June 19, 2025, 8:02am

Hi Joe, is this the error you’re currently encountering?

adventurous_hamster_08190 · June 23, 2025, 12:03pm

Yes, that looks like it.

system · June 24, 2025, 12:24am

Currently, the -t and -f commands cannot be used together.

adventurous_hamster_08190 · June 24, 2025, 11:59am

Currently, the -t and -f commands cannot be used together.

system · June 24, 2025, 3:17pm

Could you please share the CLI command you’re using and a screenshot of the error output? This will help us investigate the issue further.

adventurous_hamster_08190 · June 24, 2025, 4:25pm

The CLI command is the same as in the original post (I have redacted our API key):

apidog run --access-token [REDACTED] -f 911642 -r html --out-json-failures-separated out.json

The output is also relatively identical to my original post (I think the number after “node:” will be dynamic, and as I mentioned previously, I think the only line of importance is the “error: Error: Invalid test data.” line). See the attached screenshot.

system · June 26, 2025, 7:39am

Hi Joe,

Based on your CLI command, there might be two potential issues:

Missing environment specification
Possible incorrect folder ID in -f <folderId>

Suggestions:

Ensure you’re using the latest CLI version by running: npm install apidog-cli@latest -g
Use -e to specify environment. You can generate a new CLI command from your scenario, then replace -t <scenarioId> with -f <folderId>

To get the correct folder ID:

adventurous_hamster_08190 · June 26, 2025, 5:13pm

Unfortunately, neither of these helped.

I used the command:

apidog run --access-token [REDACTED] -f 911642 -r html --out-json-failures-separated out.json -e 3344108

adventurous_hamster_08190 · June 26, 2025, 7:36pm

One thing that’s very important–and that I mentioned but should have really stressed–is that the test run actually runs for a bit and then fails with the error. I know that at least some tests run and run to completion–the error happens minutes into the test run (I’m guessing 10 or so minutes into a 33 minute overall approximate run time).

system · June 27, 2025, 3:34am

@Joe The test data for your scenario “It should return an error if AmbassadorId is not sent in the request” has been deleted. You’ll need to save it again.

We’ll also improve this to skip such errors and continue running other valid scenarios in future updates.

adventurous_hamster_08190 · June 27, 2025, 12:32pm

That’s fantastic! Thank you for figuring that out. That’s exactly the information I needed.

I look forward to that enhancement as I think it’ll save someone else who inadvertently causes that issue.

system · June 27, 2025, 3:06pm

Thank you for your feedback. I’ll forward your request to our product team for evaluation.