-
Notifications
You must be signed in to change notification settings - Fork 26
feat: Add Client for Workorders service Test plans and Test plan template APIs #137
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
feat: Add Client for Workorders service Test plans and Test plan template APIs #137
Conversation
…dhan-ni/nisystemlink-clients-python into users/ammar/feat/test_plan_template_api
…dhan-ni/nisystemlink-clients-python into users/arvin/feat/testplan/testplans-api
…dhan-ni/nisystemlink-clients-python into users/ammar/feat/test_plan_template_api
…dhan-ni/nisystemlink-clients-python into users/arvin/feat/testplan/testplans-api
@rbell517, need you help We've reviewed the code on our end and everything looks good. I also ran the tests locally against the test environment, and they all passed successfully. However, the pipeline is failing due to a 405 error in one of the examples. It seems like the endpoint might not be available in the pipeline environment. Given that, I believe the integration test should fail in such cases. Am I missing anything? |
@ammarhusain-EMR @aravindhan-ni You will need to modify the pytest setup in pyproject.toml to tell pytest to find tests in just the [tool.pytest.ini_options]
...
testpaths = ["tests"] |
Another important note on the integration tests -- If you are creating a pull request from a fork you don't have permission to use the repo's main-test API key secret, so it will actually skip all the integration tests. You would need to make a PR in your fork and setup your own API key secret to use the github action to actually run the integration tests. I've been meaning to track down a fix to this but I haven't gotten to it. |
Co-authored-by: Richard Bell <418101+rbell517@users.noreply.github.com>
…hub.com/aravindhan-ni/nisystemlink-clients-python into users/ammar/feat/test_plan_template_api
5e41415
to
f34f0fb
Compare
…k-clients-python into users/ammar/feat/test_plan_template_api
…k-clients-python into users/ammar/feat/test_plan_template_api
…k-clients-python into users/ammar/feat/test_plan_template_api
…k-clients-python into users/ammar/feat/test_plan_template_api
Head branch was pushed to by a user without write access
What does this Pull Request accomplish?
Added Create, Delete, and Query Test plan template APIs in Workorder service.
Why should this Pull Request be merged?
This test plan template client will improve user interactivity with those Workorder Service endpoints.
What testing has been done?
Automated integration tests are included.
API Link: Swagger-link