BetterProcess HandbookBetterProcess

Standard QA Workflow Process for Software Development

Sprint Planning

Objective: Define the scope and goals of the sprint in collaboration with account owners, product managers, and the QA team.

  • Day 0 Sprint Planning: Review sprint tickets with the QA team to understand testing needs.
  • Dynamic Scope: Agile flexibility allows for new tickets during the sprint based on client priorities.

Test Case Preparation

Objective: Ensure comprehensive test coverage for all sprint deliverables.

  • Continuous Test Case Development:
    • Manual Testers: Begin writing test cases for identified sprint tickets at the start of the sprint.
    • Automation Testers: Identify repetitive manual test cases suitable for automation and update the automation suite accordingly.

Development Phase

Objective: Validate functionality and identify issues early in the development lifecycle.

  • Merge to DEV Environment:
    • All PRs are merged into the DEV environment for integrated testing.
  • Testing and Issue Management:
    • Manual Testers: Execute test cases and promptly report issues via a dedicated issue tracking tool (not Excel).
    • Automation Testers: Run automated tests with every build to perform sanity checks and identify regressions.

Issue Reporting and Resolution

Objective: Efficiently manage and resolve reported issues.

  • Clear Issue Reporting: Issues are logged with detailed information, including failing test cases and associated tickets.
  • Developer Action: Developers prioritize and resolve issues, ensuring timely fixes and updates.

Post-Fix Testing

Objective: Validate bug fixes and ensure no regression.

  • Retesting:
    • QA re-runs failed test cases post-bug fix to verify resolution.
    • Proceed to further testing only after all test cases pass.

Release Cycle Management

Objective: Ensure readiness for Beta and production releases.

  • Beta Testing:
    • After internal sign-off, release is pushed to Beta for broader testing.
    • QA conducts thorough testing in Beta, simulating production conditions.

Automation and Sanity Testing

Objective: Maintain stability and reliability through automated testing.

  • Automated Sanity Testing:
    • Automation scripts run with every build to perform quick sanity tests.
    • Issues flagged by automation are prioritized and addressed promptly.