Hi,
I have the same problem and was looking through this thread but couldn't find a solution. The issue is that the documentation for getTest doesn't list all the possible parameters that can be called, which makes the process very frustrating because you're just trying out parameter names, hoping one will work. After a lot of searching and testing, I came to the conclusion that there is no way to retrieve the called parameters through the API (which is a major flaw).
However, I noticed that the CSV export of a test case has the last column, which contains the called test parameters. Unfortunately, there is still no way to get these CSV files for each test case automatically or via the API. So, the solution I found is to manually download all the CSV files you need and save them in a folder to use as your repository for the called test parameters. This is extremely annoying and makes the process much longer than it should be, especially since this is not mentioned anywhere.
I had about 250 test cases that I had to go into and download the CSV files individually, but it only took about an hour, so I think this is the best approach for now.
If anyone has found a better solution, please let me know. I hope this issue is fixed soon because it's a major oversight in their API.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.