Test Management Process

Test Management Process

 

 

All software applications are predominantly different, running in different software and hardware environments with all manor of in-house developed programs. Testing of software cannot be set into a rigid structure and should be built and developed as the project evolves.

The following stages of the testing process are taken from the Mercury Interactive Test Director documentation. These stages can be adjusted to suit your project and define anticipated time scales

Specify Tests Requirements

Plan Tests

Execute Tests

Track Defaults

 

 

Specify Tests Requirements

 

    Define Testing

    Examine application documentation in order to determine your testing scope – test goals, objectives, and strategies.

     

    Create Requirements

    Build a requirements tree to define your overall testing requirements.

     

    Detail Requirements

    For each requirement topic in the requirement tree, create a list of detailed testing requirements. Describe each requirement, assign it a priority level, and add attachments if necessary.

     

    Analyse Requirements

    Generate reports and graphs to assist in analysing your testing requirements to ensure they meet the testing scope.

 

Back to Top

 

 

Plan Tests

    Define a testing strategy

    Examine your application, system environment, and testing resources in order to determine your testing goals

     

    Define test subjects

    Divide your application into modules of functions to be tested. Build a test plan tree to hierarchically divide your application into testing units, or subjects.

     

    Define tests

    Determine the types of tests you need for each module. Add a basic definition of each test to the test plan tree.

     

    Create coverage

    Link each test with a testing requirement.

     

    Design test steps

    Develop manual test by adding steps tot eh tests in your test plan tree. Test steps describe the test operations , the points to check, and the expected outcome of each test. Decide which tests to automate.

     

    Automate tests

    Select tests which can be automated and use testing tool ( Winrunner, QA test, Rational Robot or Visual API )

    Analyse test plan

    Generate reports and graphs to assist in analysing test planning data. Review your tests to determine their suitability to your testing goals.

 

Back to Top

 

 

Execute Tests

 

    Create test sets

    Define groups of tests to meet the various testing goals in your project. These might include, for example, testing a new software version or a specific function in an application. Determine which tests to include in each test set.

    Schedule runs

     

    Schedule test execution and assign tasks to software tester.

    Run Automated tests

     

    Execute Automated tests

    Run manual Tests

     

    Execute manual tests

    Analyse test results

     

    View the results of your test runs in order to determine whether a defect has been detected in your application. Generate reports and graphs to help analyse these results.

 

Back to Top

 

 

Track Defaults

    Add defects

    Report new defects in your application. Quality assurance testers, developers, project managers, and end users can add defects during any phase in the testing process

     

    Review new defects

    Review new defects and determine which ones should be fixed.

     

    Repair open defects

    Correct the defects your decide to fix

     

    Test new build

    Test new build of your application. Continue this process until defects are repaired.

     

    Analyse defect data

    Generate reports and graphs to assist in analysing the process of defect repairs, and to help to determine when to release the software.

 

Back to Top

 

 

www.Surfersjunkyard.com contact me on admin@surfersjunkyard.com