/v6/testExecutions - Location of Test Configuration Files

I'm getting a 404 error when trying to execute a SOAtest via the API.
/v6/testExecutions
I have been testing with the SOAtest Example Configuration config in the IDE and it works fine. In the JSON request body I tried using "user://Example Configuration" to no avail. The error message seems like the configuration file should be in the root of the workspace. Doesn't seem to be working.
If I have a Test Configuration called MyTest located in: SOAtest : User-defined -- where would this file need to exist in the workspace?
Thanks,
JT
Best Answer
-
I do want a custom config so that I can add the accessibility scans.
Are you using the new Web Accessibility Scan tool? There is nothing special to enable in the test configuration.
1
Answers
-
See Test Configuration Options for SOAtest and Virtualize Server
I see mine under "TestAssets/configs/user/Example Configuration.properties".
If you don't want to depend on a test configuration from the workspace then you can also use "builtin://Run Automated Server Tests".
1 -
Thanks. I'm pretty sure it was there, but I will retry. I do want a custom config so that I can add the accessibility scans.
0 -
I created a new Test Configuration called ABC and I exported it to /TestAssets/configs/user/ABC.properties
In my /v6/testExecutions POST request body I have general.config set to user://ABC
The error response says that the job failed with the following error: Non-existent configuration [user://ABC in workspace: ]
I also tried using user://ABC.properties and it had a similar error0 -
Yes. I've am using the Web Accessibility Scan tool. I'll try running the job with the builtin test configuration to see if it generates the report. Thanks. JT
0 -
and it does! thanks JT
0 -
Using custom test configurations in the workspace has been working for me the same way we document. It isn't obvious to me why this might not be working for you.
1 -
I checked with a colleague and we see custom test configurations working as expected. We confirmed it doesn't matter if the test configuration is added before or after starting the server. If you continue to run into issues with custom test configurations then you can enable debug logging then check the logs for detail.
1 -
Will do. If there are clear issues we will submit a ticket. Thanks JT
0 -
Thanks for being so very responsive to posts on the forum. Great product and Great support.
0