-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide an HTTP endpoint for triggering a test suite #396
Comments
I almost forget that user can run the test case via the following request: curl 'http://localhost:8080/server.Runner/RunTestCase' \
--data-raw '{"suite":"atest","testcase":"getVersion","parameters":[]}' but, we still need an API to run a test suite. |
This issue has been open 30 days with no activity. This will be closed in 7 days. |
This issue has been automatically marked as stale because it hasn't had any recent activity.If you think this should still be open, or the problem still persists, just pop a reply in the comments and one of the maintainers will (try!) to follow up. Thank you for your interest and contribution to the api-testing. |
* chore(deps): update matrixdotorg/synapse docker tag to v1.91.2 * Update app version --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: github-action update-app-version <githubaction@githubaction.com>
Description:
Now, users can trigger a test suite via the following command:
atest run -p http://localhost:9090/server.Runner/ConvertTestSuite?suite=api-testing
but, they still need download
atest
first. If we have a simple HTTP endpoint which have the same feature, it will be much handful.Why
In
CI/CD
situation, users could trigger the api testing via a simple URL. Users could use Jenkins or Argo workflows, even this endpoint could support the webhook request from GitHub/Gitlab.If the request from a GitHub/Gitlab webhook, we could even create a status against the target PR or commits.
The text was updated successfully, but these errors were encountered: