Test documentation pdf

The need for a good test plan Helps to organize, schedule and manage the testing effort  Helps in writing test cases  Improves communication with developers and with management  If d

Test documentation

 Test Plan

 Test Cases

 Test Case Design

Test plan

The need for a good test plan

 Helps to organize, schedule and manage the testing effort

 Helps in writing test cases

 Improves communication with developers

and with management

 If done correctly, it may help minimize the

documentation required

Validation Planning Issues

 Testing is intended to measure software

quality and must be planned

 It takes careful planning to select a good set

of tests

 Questions that must be answered: What to test and when to stop

Benefits of Test Planning

 Measure the cost of testing vs the confidence gained

 Forces you to work out expected results

before you run the test cases

 You can actually find errors before running

any tests!

Components of a Test Plan

Other Issues to Consider

Test Plan activities

 Use a Test Plan template, or design one

 List what cannot be tested

 Write only what you need

Test Plan activities

 Have the Test Plan reviewed

 Test while you write

 Make it a “living” document

Concerns of Test Planning

 Not enough training

 Lack of test tools

 Lack of management support

 Lack of customer/user involvement

 Not enough time

 Rapid change

 It‟s hard to say “No”

Example of a Test Plan

 Test Plan template

 Test Plan example

A Partial List for Your Test

Plans

 Title page of some sort

 Description of the testing to be done

 Updated Requirements Matrix

 List of test cases

 Traceability Matrix

 3 detailed test cases

Testing on a large project

 Roles/Responsibilities

Test Planning Tips

 Meet regularly with the Project Manager

 Plan for the test team to attend a lot of

reviews

 Make assignments early

 Assign one tester to know everything

 Have only one Test Plan

 Biggest headache: Builds

Test case

 Test Case

results, and a set of execution conditions for a

test item

 Test Suite

used to test a software program

Characteristics of good Test

Cases

 Reasonable probability of catching an error

of validating the program/system

Test Case caveats

 Errors can mask other errors

 Make sure you know how to tell whether a

test case passes or fails

 Bug fixes can cause more bugs

Where do you get your Test

 The customer: Use Cases/Scenarios

 Defects from the field or previous releases

Test Case Examples

 Test Case Template

 Test Case Example

To read more

Test Case Generation

 Case-insensitive Passwords

 State look-up

 Simple program

Case-insensitive Passwords

 Write the test cases to verify that Passwords are case insensitive when logging onto a

secure system

An example

Test Case: Verify that passwords are case

insensitive

Test Procedure:

successful)

5 Log on using Password „abcDe‟ (should be

successful).

the full name Discuss all considerations for testing such a function

Simple program

 The program accepts as input 2 integers and outputs their sum

 Assume arbitrary limits, say -100 to +100

 Design the test cases