Testing. Test plan

Testing. Test plan

When a program is complete it should be tested thoroughly to prove that it can cope with a variety of different inputs without crashing.

A Test Plan is a detailed document that describes the test strategy, objectives, estimation, results, and resources required to perform testing for a software product. 

A test Plan helps us determine the effort needed to validate the quality of the application under test. The test plan serves as a blueprint to conduct software testing activities as a defined process.

Template a test plan for project work

# Purpose Description Type of validation Test data Expected result Actual result
             

Create test plan online

Task #1

In a full-time school, a student can have 1 to 11 lessons. The form below checks the validity of the lesson number input.

Example of a Test plan for Task #1

# Purpose Description Type of validation Test data Expected result Actual result
1.1 Check the input lesson number Input valid test data Range Check 5 show a message: “Your data is correct” true

Evidence 1.1

 

1.2 Check the input lesson number Input extreme test data Range Check 11 show a message: “Your data is correct” False
Show message: “Your data is incorrect”

Evidence 1.2

 

1.3 Check the input lesson number Input invalid test data Range Check 15 show message: “Your data is incorrect” true

Evidence 1.3

 

2.1          

 

Project work. Assessment criteria

Testing Marks: 7

A collection of hardcopy test run outputs with no test plan, or a test plan with no hardcopy evidence may also be present. 
A teacher may award 1 mark if they have been shown the system working satisfactorily and there is no hard evidence in the project report.

1

There is little evidence of testing with a badly developed test plan with clear omissions. 
A small number of tests have been carried out, which demonstrate that some parts of the solution work/some outcomes of the investigation are achieved. 
2-3
There should be hardcopy evidence of most of the objectives’ test runs cross-referenced to the test plan. 
Tests include cases with valid, invalid, and extreme data. However, not all cases have been tested or not clearly presented evidence for some tests. 
4-5
The tests completed should show that the system developed has fulfilled all its objectives and demonstrates the scope of the final system. 
Tests include clear evidences for cases with valid, invalid and extreme data. 
6-7

Exercises:

Ex.1 

Create a test plan (including normal, extreme, and erroneous data) for each program described below.

a) A program calculates the average distance traveled in a week by a cyclist. Each day is
entered as a single value. The program assumes that the cyclist will travel no more
than 100 miles in a single day.

b) A program is written to store the result of a tennis match. An example of a match
result (showing the maximum and minimum values that can be entered) is 6-4, 6-7, 6-0.

c) A password program allows a user to create a password that will later be used to
access a database of club members’ personal details. The password entered by the user
should be a single word, 6 to 8 letters long.

 

Категория: Debugging | Добавил: bzfar77 (22.09.2020)
Просмотров: 4567 | Теги: Extreme data, SDLC, invalid data, testing, valid data, test plan | Рейтинг: 5.0/2
Всего комментариев: 0
avatar