Story (Required)

As a Quality Engineer, I want to establish a Continuous Integration (CI) pipeline So that I can automatically run acceptance tests for OpenShift Builds downstream And ensure the reliability and quality of our software releases.

Background (Required)

In our software development and release process, we rely on OpenShift as our chosen container orchestration platform. To ensure the reliability and quality of our software releases, it is imperative that we establish an automated process for running acceptance tests downstream of OpenShift Builds. Currently, we lack a dedicated Continuous Integration (CI) pipeline for this purpose, which results in manual testing efforts and potential delays in identifying issues. By setting up a CI pipeline for running acceptance tests downstream of OpenShift Builds, we aim to streamline our testing process, catch issues earlier in the development cycle, and accelerate the delivery of high-quality software to our customers.

Acceptance Criteria (Mandatory)

1. The CI pipeline is created using a suitable CI/CD tool (e.g., Jenkins, GitLab CI/CD, CircleCI, Tekton) and is version-controlled in a dedicated repository.
2. The CI pipeline triggers automatically when a UMB message is consumed via CPaaS
3. The CI pipeline integrates with OpenShift, utilizing appropriate CLI tools, API access, or automation scripts to interact with the OpenShift platform.
4. The acceptance tests suite is integrated into the CI pipeline and configured to run automatically after deployment to the OpenShift downstream cluster.
5. Acceptance tests should cover essential use cases and verify the functionality, security, and performance aspects of the application.
6. Test results are captured and reported within the CI/CD platform, including any failures or issues encountered during the acceptance tests.
7. In case of test failures or issues, the pipeline should notify the relevant team members or stakeholders, providing sufficient information to investigate and resolve the problems.
8. Secrets, environment variables, or credentials required for accessing the OpenShift cluster or other resources are securely managed and stored.
9. The CI pipeline and associated configurations are well-documented, including setup instructions, environment requirements, and troubleshooting guides.
10. The CI pipeline is regularly maintained, and updates are applied as needed to accommodate changes in the application or OpenShift environment.
11. The setup should adhere to best practices for CI/CD, OpenShift, and test automation.

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Done Checklist

• The CI pipeline is successfully set up and integrated .

• Acceptance tests are executed automatically , and test results are accessible within the CI/CD platform.

• Any necessary notifications or alerts in case of test failures are configured and functional.

• Documentation is complete and shared with the relevant team members.

• The CI pipeline passes a review and validation process by relevant stakeholders.

By completing this user story, we aim to ensure that our software changes are thoroughly validated through automated acceptance tests on the downstream OpenShift environment, enhancing the overall quality and reliability of our releases.