TestProject does indeed support data driven testing via CSV files.
You can parameterize your API calls by doing the following:
- Create parameters for the required fields in the API call:
Save it and then select it for the field:
You can create more parameters for the other fields or you can hard-code them in the test.
- When you’re done setting up the parameters, you can exit the test, and find it in your project, and from there generate a data source template, this will download a CSV file for you including your parameters as headers:
You can fill in the rows in the CSV file, each row will be a single execution of the test, and each parameter will receive the value you have given it in the row for that execution.
e.g. if row 1 has the values A,B,C, during that execution, the EXPECTED_STATUS will be A, MY_QUERY will be B and MY_URI will be C.
Remember, more rows will be more executions.
Once you’re done save the file and move to the next part.
- You can upload the CSV file to TestProject and attach it to a test in a job or use it when executing a singular test.
You can upload the file from here:
Or when executing a test case:
And to attach them to test cases in jobs, just select the data sources icon:
And select one from the list or add a new one.
To answer your original question, you cannot use the proxy jars inside other addons, you can use them if you create tests (not addons) using the original TestProject SDK which is now classified specifically as the addon SDK:
If you would like to view a usage example, you can record a test with an addon and generate it’s code.