EKS Testing: Reliability team; MVP testing with the unauthenticated endpoints

[jennb33]

User Story

As the Reliability team resources, We need to perform the EKS MVP testing with the unauthenticated endpoints, So that any errors with the unauthenticated endpoints can be discovered and mitigated before being released to a live environment

Issue Description

Postman tests have been assembled into a single collection in Postman cloud account, and the Postman test collection is stored in the Platform Postman Cloud account VA.gov Platform Reliability Team | Public APIs | Postman API Network. Postman test collection is configured to prepend request urls with an environment variable env_url Refer to general Postman best practices – Document Your API Like a Pro: Postman Collection Best Practices | Postman Blog

Tasks

• [ ] Postman test scripts are retrieved into the postman/newman container provided by the PRT through Docker hub and executed by the default postman installation in the container
• [ ] Exception Handling: Exceptions while executing tests are reported as a test fail
• [ ] Document MVP testing and outcomes of testing in the Test Plan Confluence documentation

Success Metrics

Testing will be completed with a low error rate. Any outstanding issues that are discovered during testing need to be ticketed separately for mitigation work.

Acceptance Criteria

• [ ] Testing the MVP EKS work with unauthenticated endpoints is complete
• [ ] Documenting the testing work process and outcomes
• [ ] Documenting future work that are outcomes from testing

---

Validation

Assignee to add steps to this section. List the actions that need to be taken to confirm this issue is complete. Include any necessary links or context. State the expected outcome.

[IGallupSoCo]

Vets-api branch with the collection added at a root level.

[IGallupSoCo]

[IGallupSoCo]

Local manipulation of the target url is working as intended.