Skip to content
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

Automatically registers nightly test runs in CAE TestRail #206

Merged
merged 8 commits into from
Jun 7, 2023

Conversation

nutjob4life
Copy link
Member

🗒️ Summary

Merge this to resolve devops#35 which'll do the following:

  • Update the Jenkins pipeline so that TestRail credentials are available
  • Instantiate a service in the Docker Composition that runs Newman tests with the TestRail Reporter, using the credentials from above
    • In addition, it uses TestRail project ID 168 (which is PDS)
    • And TestRail suite ID 12824 (which is "PDS Registry API, automated tests")
  • Adds the test case ID C1274687 to a single test (with three assertions) in the Postman collection (which is "As an API user, I want to search by a temporal range as an ISO-8601 time interval")

⚙️ Test Data and/or Report

♻️ Related Issues

🔮 Future Work

  • The test case ID C1274687 is recorded in the postman_collection.json file only, not in Postman. Suppose someone were to fire up Postman and add a new test. Exporting a fresh postman_collection.json file would overwrite all test case IDs. The test case IDs should be in Postman itself (i.e., each pm.test("Summary of assertion being made", …)pm.test("C1234567 Summary of assertion being made", …)
  • PDS Jenkins has secrets in order to pass along to the TestRail reporter so it can use the TestRail API to register the results of Newman tests. These credentials currently consist of a username and an API key. The username is Sean.C.Kelly@jpl.nasa.gov. We should have a "service" account instead, since despite my rare use of public transportation, I could still get hit by a bus.

@ramesh-maddegoda ramesh-maddegoda self-requested a review June 7, 2023 01:15
Copy link
Contributor

@ramesh-maddegoda ramesh-maddegoda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

Copy link
Member

@tloubrieu-jpl tloubrieu-jpl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That sounds good Sean, thanks. I think it is a very good candidate for a demo this Thursday.

@nutjob4life nutjob4life merged commit 74c1ef5 into main Jun 7, 2023
@nutjob4life nutjob4life deleted the devops#35 branch June 7, 2023 13:24
@nutjob4life
Copy link
Member Author

@tloubrieu-jpl I agree! However, I'm out this Thursday taking all day training ("Understanding Space").

If you want to run the demo, go for it. It's easy. I can tell you the steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

As a EN team member, I want to check the API test reports in testrail
3 participants