Scribd
Upload
10 views18 pages

Program Testing and Maintenance

The document outlines the importance of a test strategy and plan in the program development lifecycle, detailing the types of tests that need to be performed to ensure the program meets its requirements. It categorizes test data into normal, abnormal, extreme, and boundary types, emphasizing the need for thorough testing. Additionally, it discusses the necessity of ongoing program maintenance, which includes corrective, perfective, and adaptive maintenance to address errors and improve functionality.

Uploaded by

dc1901020
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
10 views18 pages

Program Testing and Maintenance

The document outlines the importance of a test strategy and plan in the program development lifecycle, detailing the types of tests that need to be performed to ensure the program meets its requirements. It categorizes test data into normal, abnormal, extreme, and boundary types, emphasizing the need for thorough testing. Additionally, it discusses the necessity of ongoing program maintenance, which includes corrective, perfective, and adaptive maintenance to address errors and improve functionality.

Uploaded by

dc1901020
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 18

Program testing and maintenance

There needs to be a test strategy set out in the analysis


stage of the program development lifecycle showing an
overview of the testing required to meet the requirements
specified. This shows how and when the program is to be
tested.

In order to clarify what tests need to be performed, a test


plan is drawn up showing all the stages of testing and
every test that will be performed. As the testing is carried
out, the results of the tests can be added to the plan
showing that the program has met its requirements.
Likely contents of a test plan
In the first instance, an outline plan is designed, for example:
flow of control: does the user get appropriate choices and does the chosen option
go to the correct module?
validation of input: has all data been entered into the system correctly? do loops
and decisions perform correctly?
is data saved into the correct files?
does the system produce the correct results?
This outline test plan needs to be made into a detailed test plan.
Test data for test plan
Normal test data that is to be accepted by a program and is used to show the program is working
and expected

Abnormal test data that should be rejected by a program as it is unsuitable or could cause
problems

Extreme test data that is on the limit of that accepted by a program for example when testing the
validation rule such as number >= 12 AND number <=32 the extreme test value will be 12 at the
lower limit and 32 at the upper limit ; both these values should be accepted

Boundary test data that is on the limit of that accepted by a program or data that is just outside
the limit of that rejected by a program e.g when testing a validation rule like number>=12 AND
number<=32 the boundary test data would be 12 and 11 at the lower limit and 32 and 33…
Test data continuation…
at the upper limit. 12 and 32 should be accepted, 11 and 33 should be rejected.
The need for continuing maintenance of a system and the
differences between each type of maintenance
Program maintenance is not like maintaining a piece of equipment by replacing worn out parts.
Programs do not wear out, but they might not work correctly in unforeseen circumstances. Logic
or run-time errors that require correction may occur from time to time, or users may want to use
the program in a different wav.
Program maintenance can usually be divided into three categories:
• Corrective maintenance: is used to correct any errors that appear during use, for example
trapping a run-time error that had been missed during testing.
• Perfective maintenance: is used to improve the performance of a program during its use, for
example improving the speed of response.
• Adaptive maintenance: is used to alter a program so it can perform any new tasks required by
the customer, for example working with voice commands as well as keyboard entry.

You might also like