Testing & Evaluating Software Solutions

Reporting on the Testing Process

Syllabus

Documentation of the test data and output produced. Use of CASE Tools

Communication with those for whom the solution has been developed, including: Test results Comparison with original design specifications.

Why do we need to report?

Testing is a vital part of software development, but unless it is reported accurately there is no way to gain a full understanding of the solution.

Problems need to be highlighted and acted upon regularly.

Documentation of the Testing Process

1. Test Requirements (What needs to be tested)

Reflect on the objectives and design specifications.

What tests need to be undertaken, why? All aspects of the entire system should be

tested.

Documentation of the Testing Process

2. Test Plan (How do we implement the tests?)

Include a schedule and time line of events. Include and document the use of CASE

tools.

Documentation of the Testing Process

3. Test Data & Expected Results (What are the inputs and expected outputs)

All test data and expected results should be documented.

If modifications are made then the entire testing process needs to be run again.

Identify why the entire testing process needsto run again for minor module modifications

Documentation of the Testing Process

4. Test Results (Do actual results meet expected results?)

All results should be kept for justification and evaluation.

They can also be used to confirm that modifications have been made.

Documentation of the Testing Process

5. Recommendations (What needs to be done now?)

Bugs have been identified so therefore strategies must to employed concerning how to fix them.

All bugs should be accessed concerning severity.

1. Dialog box not centred 2. Logic Error when getting results

Communication of Process

Communication is an important practice in the overall completion of software development, but also in regards to testing.

This communication must take place between: Developers and client Outsourced testers and developers

Developers and Client

This communication should address objectives that have not been met.

Communication should also be non-technical.

The provision of graphical methods to display data will help clients develop a mental image i.e. Onsite practical demonstration and checklists

Communication with Developers

Sometimes the testing process is outsourced to testing departments or forms.

All findings and evaluations should be clearly presented and supported with specific facts.

A climate of cooperation should be evident between all parties in this process.

Use of CASE Tools

It is appropriate and often necessary for developers to use specialised CASE tools as they provide structured assistance, sometimes automated processes and development of test data.

Example 1 – Test data generator

Name – Win Runner

Function – It is a functional testing tool. It

creates a variety of test data items to be entered

into a system and analyses expected with actual

output.

Example 2 – Volume Tester

Name – LoadRunner

Function – Is a simulation program that tests

simultaneous use. Through the creation of

virtual users a simulation is created. All results

are evaluated for developers.