Test Management Process

Test Management Process:

·         Specify System and business requirement

·         Create test plan.

·         Develop & Executes test Cases.

·          Track defects.

Specifying requirement:

Analyze your application/System and gather business requirement, then start determining testing requirement:

·         Define testing scope:

§  Integration.

§  UAT (User Acceptance Test).

§  Performance.

§  Security.

·         Create requirement (Test Requirement):

§  Build you RTVM (Requirement Tractability and Verification Matrix)

§  Make space to fill later on with test cases developed under each scope.

·         Detail requirements:

§  Create a list of detailed testing requirements for each requirement in RTVM.

§  Assign priority level for each requirement detail.

·         Analyze requirements.

 

Create test plan:

·         Write your master test plan.

§  Introduction.

§  Objective.

§  Scope. (In Scope & Out Scope)

§  Entry criteria.

§  Exist criteria.

§  Assumptions.

§  Functions and features to be tested.

·         Write detailed test plan if there is more than Application/System/Module  to be tested.

 

Develop & Executes test Cases:

·         Write test cases for the previously specified test requirement.

·         Use one of testing tools like HP Quality Center (QC).
QC acting like a central repository that store all test related information like:
Note: I will make separate post about HP Quality Center

§  Releases.

§  Cycles.

§  Business requirements

§  Test cases

§  Test scenarios.

§  Defects.

·         Execute test cases.

 

Track defects:

·         Raise a defect against the failed test cases.

·         Re-Test the defect after applying the fix.

·         Keep track with number of defect in the system and number of failed test cases.

·         Analyze and find which requirement tested successfully and which one failed.