Goal of this epic

High level goal of this epic is for AppStudio QE team to get familiar with the service and the team creating it, get to know the technologies used, get familiar with processes (where the code lives, where issues are being tracked, what CI/CD pipeline is the service using, ...) and then draft a initial plan for ensuring quality assurance.

Get to know the team

• Schedule a call with the team/teamlead to discuss the state of QA in this particular service
• Know where the code lives
• Investigate current/planned CI/CD pipelines
• Discuss with the team their dependencies & contracts with other services
• Subscribe to the team's communication channels (JIRA, Slack, mailing list, ...)

Assess current state of QA in service

• Go through what tests are being run against that service (compare this for example with https://source.redhat.com/groups/public/quality-engineering/quality_engineering_wiki/test_types_levels_and_importance_rev_10)
• Analyze current state of tests and propose "next big improvement" (introduce a new test type, like for example contract testing. Or just suggest improving on some existing level of testing(for example unit tests, or test coverage monitoring))