Services

Web Application Testing Process

PHASE THROUGH WHICH A PROJECT GOES

1. Requirements
2. Test Design
3. Test Execution
4. Deployment

REQUIREMENTS
Client requests a projcect. Below documents are needed before a project gets into QA.

1. Web Requirement document
2. Functional specification document
3. Technical specification document
4. Development schedule
5. Architectural and Technical walkthrough (front-end & back-end)
   

TEST DESIGN

1. Review spec
2. Create test plan.
3. Define High Level QA project plan
4. Give input to schedule (set milestones & targets)
5. Define test cases
6. Define test procedures
7. Test plan walkthrough - get feedback
8. Incorporate feedback (if any)
9. Define performance requirements
10. Finalize QA project plan & schedule

TEST EXECUTION

1. Get environment ready
2. Run test cases
3. Start writing automation test scripts
4. Write and report bugs
5. Verify fixes and close bugs appropriately
6. Prepare QA status report at end of week for Project meetings
7. Configuration testing
8. Regression testin
9. Integration testing (when the code is ported to live site)

DEPLOYMENT

1. Live testing plan (run MATs)
2. Go live
3. Live System testing
4. Post Mortem

CRITICAL ISSUES
Before starting a project:

1. Functional spec, Technical spec, Navigation map, Back-end gathering, Performance requirements UI spec and Field validation spec are needed.
2. QA input should be incorporated into the schedule before putting out the final time schedule of Project.
3. Avoid surprise feature additions.
4. Release notes should be given with each build.