Hi Team,
We have been using Apidog for several months now to safeguard our API development processes and are really happy with the features it provides for automated execution of test cases in our Azure Devops Pipelines.
But, we’re still relying on the Command Line instruction, which is a great way to get started but to scale out over multiple teams is less convenient.
apidog run https://api.eu.apidog.com/api/v1/projects/{projectId}/api-test/ci-config/{ciConfigId}/detail?token={token} -r cli,junit
We can not copy the individual ID’s and token from the command line suggested in the UI (it copies the whole command).
Using the “Export Data” approach would mitigate this burden, but since it can not be integrated directly in a SCM repository (e.g. Git), changes are not tracked. Also, it creates an additional step of exporting and uploading the data set each time a change has been made.
My proposition is two-fold:
- Create a native Azure Pipline Task with the following input parameters:
- projectId
- ciConfigId
- token
- optional region (for EU users)
- optional report type list (e.g. cli,junit)
- task: ApidogTest@1
displayName: Run Apidog Test Scenarios
inputs:
projectId: #The ID for the project in Apidog
ciConfigId: #The ID for the Test Scenario configuration
token: #The Apidog token for executing the Test Scenarios
region: #Optional setting for EU users
reportingTypes: #Optional list of reporting types (e.g. cli,junit)
- Integrate Test Cases in SCM for tracking changes and allow for extracting (or generating) and running a Test Scenario Cases JSON-file.
The first solution would be awesome to have, making it a lot easier to onboard other teams in adopting Apidog for safeguarding quality of their APIs, the second would just reduce overhead of exporting, committing separately and remembering to do so each time a test case is changed.
