QA Process

QA Process

1. 1 - Analysis: Refinement and Analysis meetings

   • 1 - QA Questions
   • 2 - Acceptance criteria definition
   • 3 - High level Test Plan
   • 4 - Update JIRA information Ticket

2. 2 - Development and Testing

   • Developers working on a new product
     • 1 - Test plan design
       • Test Rail Test (if it's no performance test)
     • 2 - Test design (Unit integration, E2E, manual test)
     • 3 - If its necessary -->Briefing between QA and Dev
     • 4 - SonarQube quality code analysis
   • Tester verifying the new product
     • 1 - Create Pull Request (to merge to dev branch)
       • 1 - Send mail (team)
       • 2 -Unit/Integration test starting to execute
     • 2 - (Optional) Specify automatic test execution (unit/integration/E2E)
     • 3 - Manual Test Execution
     • 4 - Maintenance task
       • Fix old design
       • Fix old test
       • Document task/test

3. 3 - UAT process: Verify new functionality

   • 1 - Record evidences or create a confluence page (performance test)
   • 2 - Send UAT email
     • Affected user (if it's a defect) or Alvaro
     • Team

4. 4 - Review: Developers & Testers check finished functionality

   • 1 - Update JIRA task (business description, title, UAT link, subtask, etc)
   • 2 - (Optional) Test review between QA members
   • 3 - Pull Request accepted by all reviewers
     • 1 - Merge code through the pull request
     • 2 - Fill "Fix Version" field on JIRA to include the task into the new release

5. 5 - Dev branch process: When new code is merged in DEV branch

   • 1 - Verify unit test and integration test were executed correctly
   • 2 - E2E execution
   • 3 - Prepare PreRelease meeting