Software Test Management

WHAT IS TEST PLANNING ?

Test management is the movement of supervising a few tests. A test management instrument is programming used to administer tests (robotized or manual) that have been long ago specified. It is regularly connected with robotization programming. Test management instruments frequently incorporate necessity or detail management modules that permits immediate era of the prerequisite test grid (RTM), which is one of the primary measurements to demonstrate utilitarian scope of a framework under test (SUT).

SOFTWARE TESTING LIFE CYCLE

• TEST PALING

I.            Define test  strategy

II.            Estimation of test cases

III.            Plan the resources such as man power, tools, requirement

• TEST DESIGN

I.            Identify the areas of risk

II.            Develop a test case format

III.            Prioritise test case plan according to every phase of SDLC

IV.            Prioritise the test cases

V.            Mapping items to test cases

VI.            Creating  test procedure specification

• TEST EXECUTION

All the test cases are executed and the results are documented

• Post execution

I.            Understanding the  bug

II.            Reproducing the bug

III.            Analyzing the nature of and causes of the bug.

 

 

TEST PLANNING

A software test plan is a document that describes the goals and objective of test approach, focuses of a software testing efforts. The process of preparing a test plan is a very to think through the efforts needed to validate the acceptability of a software product. This document will help the outside people understand why and how product validation.

TEST PLAN COMPONENTS

• TEST PLAN IDENTIFIER

Each test plan should assign unique identifier so that it can be associated with a particular project. All project related document is stored in database

• INTRODUCTION

In this section the test planner  gives overall description of product  this includes software module being test,  particular features being tested. It includes organizational standards, quality assurance plan etc.

• ITEMS TO BE TESTED

This component consist items ,modules ,procedure, library, subsystem in software to be tested  should include name, identifier as mentioned earlier. These references support the tester with traceability tasks.

• ITEM PASS / FAIL CRITERIA

There should some way to tester to determine whether test has been passed or failed upon the execution of test case on software. This component consists of detailed description of test cases. This component is very important for testers.

• TESTING ENVIRONMENT

Here testing environment consist of software, hardware, and necessary  tools required to perform testing. In  this component test planner describes testing environment.

• TEST METHODS

Test routines in the test arrangement state how test scope will be accomplished. Test systems may be dead set by guidelines, administrative orgs, or contractual assertion, or might must be made new. Test strategies additionally indicate test supplies to be utilized as a part of the execution of the tests and build pass/fail criteria. Test systems used to check fittings plan necessities can run from extremely straightforward steps, for example image based assessment, to expound test methodology that are recorded independently.

• SCHEDULE

Here test planer describe the time duration needed to complete the testing.  Planer sets the test milestone, record etc.  testing should be completed within assign time period only.