Purpose (the why):   

• We want to build software that solves problems, not creates them.  Writing some test automation will help us keep ourselves accountable and confident which is in everyone’s best interest.  If done right, test automation should help the project’s overall velocity by making sure changes are not introducing regressions.  In addition, these same tests can be used to gate deployments and  “monitor” how prod functionality is working today.

Responsible: 

• App Team QE Lead, App Team Product Manager

Prerequisite/dependencies:  

• Business requirements.

Next task: 

• Create an IQE test plugin. 

Deliverable/completion criteria: 

• You have reviewed the QE Onboarding Guideline and have completed the steps in the “Getting Started” section.
• Create an IQE plugin.
• Identify service requirements in the codebase.
• Automated tests that create confidence around those requirements.
• Production test results reporting.

Expected duration/effort:  

• Ongoing, as the service evolves.

Due date: 

• Before GA

Supporting documentation/best practices: 

• https://insights-qe.pages.redhat.com/iqe-core-docs

How to get help:

• Contact Dave Johnson (quality engineering)