QA Process Guidelines

 As part of QA, we need to follow a few guidelines to deliver the product fast and with quality.

Few of the guidelines are as follow:

• QA Process

  • Add postman collection for new API's in the existing collection as part of sprint story (create a sub-task)

  • QA should do PRD review before even picking any sprint task and figure out issue there itself

  • Identify critical scenarios before dev start coding and share your feedback upfront

  • Add test cases in JIRA and share it with dev/PM for review before dropping a build to QA.

  • Ask the dev team to test the critical scenarios by themselves and need to publish the Test Results.

  • Ask dev team to publish unit test report

  • Look into big impact of the sprint story from an application perspective instead of checking specific task

  • Create a checklist for production release

  • Each team member should monitor Crashlytics report after the release

  • Always add first-level analysis in the defect including Request/Response, back-end, mobile application logs

  • Verify logs as part of sprint story testing. If logs have been added for the feature, it helps to debug any issue on the feature

  • QA should take all necessary access to debug the issue so they can do first-level analysis by themselves

  • Enhance App Regression Suite with every release

• Ask dev to verify APK from their end for few critical cases before sharing with QA

• QA should own deployment on staging/QA env

 

• Prod Bugs RCA

  • Template to write RCA in JIRA

    • Description of the issue

      • Application Version

      • Android/iOS Version

    • Steps to reproduce

    • Impact

      • App crash impact

      • Orders impacted

    • The root cause of the issue (how it introduced)

    • How can we avoid this issue in future or similar issues

    • Time took to reproduce the issue

    • Tag/Label issue type (Functional/Performance/Infra)

• QA Involvement

  • Get a detailed understanding of the issue so we can tag the issue correctly

  • QA of the POD/Team should take responsibility w.r.t issue raised

 

• Automation

  • Each team member should follow automation guidelines while writing code

  • Identify smoke test suite to automate

  • Everyone in the team must automate test cases

  • At least 50% of sprint tasks must be automated

 

• Postman Collection

  • Each team member responsible to maintain postman collection w.r.t his deliverables.