Plan QA Schedule for Release

I am documenting all the following points on the basis of my experience, if you find any ambiguity; please provide me your valuable feedback comment so that I can make the corrections.

Before you plan any QA Schedule for the release, consider the following points to take:
  1. Name of Release
  2. List of various tasks
  3. Expected duration for particular task
  4. Expected start of particular task
  5. Expected finish of particular task
  6. Resources to be involved in particular task
  7. Actual start of particular task
  8. Actual finish of particular task
  9. Predecessors
List of high level tasks in the Release
  1. Planning
  2. Analysis
  3. Design
  4. Execution
  5. Reporting
  6. Closure Activities
Tasks activities in planning phase
  1. Get Dev Schedule to build QA Schedule (Dependency)
  2. Get Environment Information
  3. Finalize Test Schedule
  4. Create Scope Doc
Tasks activities in Analysis phase
  1. Analyze BRS & Mockups and Send Questions/Findings
  2. RAA session to answer questions
  3. Review and Analyze RAA Answers and prepare list of changes to TCs
Tasks activities in Design phase
  1. Develop positive and negative Test Scenarios
  2. Review Scenarios
  3. Develop positive and negative Test Cases
  4. Peer Review of Test Cases + Fixing Findings
  5. Create RTM
  6. Copy TCs to Other Test Beds Folders (after Review and Before Execution)
  7. Create Test Data (if needed)
MILESTONE: Test cases are finalized - Execution can begin

Tasks activities in Execution phase
  1. Smoke Test
  • Select Smoke Test Cases to be executed
  • Execute Smoke Test Cases
  • Evaluate Build (Functional Test GO/No GO)
  1. Functional Cycle
  • Execute test Cases
  • Retesting fixed bugs
  1. Regression Cycle
  • Select Test Cases to be executed
  • Start Code Freeze & Execute Regression test Cases
  1. Defect Management
  2. Buffer/Contingency- Unexpected delay from Dev/QA, Unexpected failures, bugs not fixed from first time, bad deployments, …etc
  3. UAT Cycle (release day)
  • Execute test Cases
  • Give feedback (Production GO/ No GO)
Tasks activities in Reporting phase
  1. Give TCs Development Report
  2. Give Execution Report
  3. Give Defect Report
Tasks activities in Closure Activities phase
  1. Fill in lessons learned sheet
  2. Consolidate & Give Lessons Learned sheet
  3. Get Sign off
Abbreviations
RAA – Requirement Ambiguity Analysis
RTM – Requirement Traceability Matrix
UAT – User Acceptance Testing
TC – Test Case
QA – Quality Assurance

No comments:

Post a Comment