Story (Required)

• As a QE running single e2e tests in pipleines, I want e2e test execution resources to be acccessible locally without needing to rely on upstream configuration. 

Background and Approach (Required)

• Update our TEST_IMAGE with resources that are usually pulled from upstream during the test execution. 
• This should give us better control and input into the resouces needed during test execution. 

Out of Scope

• Investiations into any e2e test failures. 

Dependencies

• N/A

Acceptance Criteria (Mandatory)

• Single test pipelie excutes and utlises resources from Test_image

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Ensure code coverage is not reduced with the changes.
  • Integration tests have been automated.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested and merged on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written (if applicable).
• Build:
  • Code has been successfully built and integrated into the main repository / project.
  • Midstream changes (if applicable) are done, reviewed, approved and merged.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.