Académique Documents
Professionnel Documents
Culture Documents
Marketing Requirements
Target Date planned for the Releases and decision on the entire Project schedule that is required
to achieve these target dates.
This includes the decision on Design Specifications (Productwise), review of the design specs
and development schedule. This involves QA during the phase of review.
Test Plan : This is a top-level document that talks about how the product is going to be tested
This includes Objectives, Methodology adopted while testing, Features to be tested and not to be
tested, risk criteria, testing schedule, cross-platform support and the resource allocation for
testing.
Feature Test Plan : This document talks about how the testing is going to be carried out for
each type of testing.
This document includes technical details (Software requirements) required prior to the testing. It
is important from the testers point of view to understand and plan the technical resources prior
to the testing.
Application Development : Considering the product features, tester has to make ready his/her
own test suit.
Build Procedure :
QA Testing :
QA Extensive testing :
Cross-platform testing
Stress testing and memory leakage testing.
QA Testing :
CDs are cut for the released products and the product is installed using those CDs and it takes
place in San Jose.
A review meeting to analyze the performance of the product, which is set, and the same is
compared with the objectives set.
Post-release Scenario :
One branch is kept for the post release modification and hence the product testing.
Post release review meeting to decide upon the objectives for the next release.