Best Practices and Examples

Automated E2E tests should validate the primary user paths supported by the service under test. The actions performed in the E2E tests should follow the same sequence as the user's actions. Tests should include coverage for the user paths followed in the service's quickstarts.
 
For example code see:

Repo:
https://github.com/bf2fc6cc711aee1a0c2a/e2e-test-suite

Pipelines:
https://gitlab.cee.redhat.com/mk-ci-cd/mas-ci/-/tree/master/src/io/mas/ci/pipelines/e2e
https://main-jenkins-csb-mas.apps.ocp-c1.prod.psi.redhat.com/job/e2e-test-suite/

Test results are available here:
Reportportal - https://reportportal-cloud-services.apps.ocp-c1.prod.psi.redhat.com/ui/#rhosak/launches/115

Where to Get Help

Contact the MAS QE team (managers ldimaggi@redhat.com and rhn-engineering-jcoleman).