1/31/2021 IGCSE ICT - Systems Analysis and Design - Testing the System

Section 7.5:
Stage 3b - Testing a System

Learning Objectives

Understand what is meant by systems testing.

Know the difference between unit testing and whole-system
testing.
Be able to create a test plan, using normal, extreme,
abnormal and live test data.

Stage 3b - Testing
Testing individual modules (parts) of the system
# When each module (part) of the system has been created it must be tested to make sure
that it works correctly.

Examples of modules that should be tested include:

Data structures - do tables hold data correctly?

Validation rules - does the system reject unreasonable/incorrect data?
Input screens - does each form control allows users to enter data correctly?
Output screens - are output results correct, clear and complete?

Testing individual parts (modules) of the system is known as unit testing.

# Any errors found will be corrected by the person who created the module (a programmer
for example).

# The module that failed the first test will then be re-tested to make sure that the error has
been fixed.

file:///F:/FRAVASHI/ICT/IGCSE ICT - Systems Analysis and Design - Testing the System Part 5.html 1/4
1/31/2021 IGCSE ICT - Systems Analysis and Design - Testing the System

Using a test plan

# Testing a system involves creating and using a test plan.

# A test plan should be created for each system module should list all of the different
tests that we are going to perform.

A good test plan should be created for every system module and include...

* A list of the tests that are to be performed

* The data to be used in the test
* The type of test -(normal / extreme / abnormal / live)
* The expected outcome of the test
* The actual outcome of the test should be logged (Data accepted / rejected).

Testing with normal, extreme and abnormal data

# A test plan should always use four types of testing data:

Normal data
Extreme data
Abnormal data
Live data

file:///F:/FRAVASHI/ICT/IGCSE ICT - Systems Analysis and Design - Testing the System Part 5.html 2/4
1/31/2021 IGCSE ICT - Systems Analysis and Design - Testing the System
Scenario:
Imagine we were testing a system module (text box) to make sure that it will only accept
entries of numbers between 1 and 5. The test data would look like the example in the
table below:

The first three types of test data would be used to test the system BEFORE it
was delivered to the customer.

Type of test Description Example

data

Normal data Data which should be accepted and The numbers 1, 2, 3, 4 or 5

pass the test without any problems. should be accepted.

(In our example, this was any number

between 1 and 5)

Extreme data Data which is on the border of what Using the same scenario as
the system will accept. above, the numbers 1 and 5
would be used to test the
borderline data.

Abnormal data Data that should not be accepted by Examples of data that should
the system. be rejected by the system
could be 0, 6, Two, Hello,
(In our example, this is any data other etc.
than 1, 2, 3, 4 or 5)

Live data (below) is used to test the system AFTER it has been installed into the
customer's workplace.

Type of test Description Example

data

Live data Data that is actually used in the Once installed into the
customer's company. customer's workplace, all
modules would be tested
with real-life data that the
company actually uses.

An example test plan

# The table below demonstrates an example test plan that could be used to test a system
module that will be used to accept the age of a driving test candidate.

The cell should accept ages within the range of 17 - 70 . Any other data should be
rejected:

Test Data entered Type of test Expected Actual

number (test mark) data outcome outcome

1 20 Normal Accept This section

would be filled in
2 45 Normal Accept by the tester
and will log
3 59 Normal Accept what actually
happened as a
4 17 Extreme Accept result of each
test.
5 70 Extreme Accept
If any of the
6 Thirty Abnormal Reject
actual outcomes
(error message)
were different
7 16 Abnormal Reject to the expected
(error message) outcome, the
module would
8 71 Abnormal Reject have to be
(error message) corrected and
then re-tested.
9 -10 Abnormal Reject
(error message)

file:///F:/FRAVASHI/ICT/IGCSE ICT - Systems Analysis and Design - Testing the System Part 5.html 3/4
1/31/2021 IGCSE ICT - Systems Analysis and Design - Testing the System

Testing the system as a whole

# Once individual parts of the system have been tested and any problems solved, the
system will be tested as a whole.

Testing the system as a whole is known as integration testing.

# Testing the system as a whole makes sure that all of the individual modules work with
each other correctly.

For example:
A data entry form might allow a user to enter their date of birth correctly but when
submitted, this data might not be visible on the report.

# Any problems found during whole system testing will be corrected and then re-tested.

file:///F:/FRAVASHI/ICT/IGCSE ICT - Systems Analysis and Design - Testing the System Part 5.html 4/4