Scribd
Upload
8 views14 pages

ICT Notes+Chapter+7.4+Testing

Chapter 7 focuses on testing strategies for a new system, outlining the definitions and types of testing such as function/unit testing, module testing, and final testing. It also describes the importance of a test plan and test design, detailing the necessary components and types of test data, including normal, extreme, abnormal, and live data. The chapter emphasizes the systematic approach to ensure all parts of the system function correctly and meet expected outcomes.

Uploaded by

muazbinmofazzal669
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
8 views14 pages

ICT Notes+Chapter+7.4+Testing

Chapter 7 focuses on testing strategies for a new system, outlining the definitions and types of testing such as function/unit testing, module testing, and final testing. It also describes the importance of a test plan and test design, detailing the necessary components and types of test data, including normal, extreme, abnormal, and live data. The chapter emphasizes the systematic approach to ensure all parts of the system function correctly and meet expected outcomes.

Uploaded by

muazbinmofazzal669
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/ 14

CHAPTER 7

7.4:

TESTING

MS. MASARRAH
Learning objectives
❖ Create test designs and strategies for
the new system.

❖ Describe the test strategy, test plan


and test design, test data and live data.
Stage 3:
Testing

• DEFINITION: Every part of the system will be checked in order to locate any
errors. Checking, using sample data that all parts of the system function as
expected.
TEST STRATEGY
• DEFINITION: A set of guidelines explaining how the testing will be carried
out.
• It describes the approach that the team will take during the testing that can
be done during the development of the software as well as when it is
completed.
• Types of testing strategies are:
➢Function/Unit testing
➢Module Testing
➢Final testing (or terminal testing)
Function/Unit Testing

❑ Testing of an individual software component.


❑ It is typically done by programmer and by testers.
❑ It requires detailed knowledge of the internal program
design and code.

❑ Example: Taking students’ attendance function in a


teacher module for Real School (Engage)
Modules Testing

❑ DEFINITION: A part of a computer program that carries out a


particular function of the program.
❑ It is a procedure for testing the subprograms/subroutines/
subfunction.
❑ Done by the tester.
❑ Recommends testing the smaller building blocks of the program.
❑ Example: Teacher module for Real School (check all the functions
that the teacher can do).
Final Testing

❑ DEFINITION: Tests carried out on the whole system once it has been
completely developed.
❑ Making sure all of the individual modules works with each other
correctly.
❑ Example: Testing the whole Real School system (Engage).
TEST PLAN

• DEFINITION : A document that lists and describes all of the tests that will be
carried out to thoroughly test the new system.
• It should contain tests for:
➢Data and file structures such as tables and fields.
➢Input formats
➢Output formats
➢Validation routines
TEST DESIGN

• DEFINITION : a detailed description of a particular task listing test data,


expected results and actual results.
• The test design for each test should show details such as:
➢What is being tested
➢The test data that will be used
➢The expected outcomes
➢The actual outcomes
➢Space so that any remedial actions taken to correct errors can be described.
• Remedial action: steps taken to correct an error.
TYPES OF TEST DATA

• One of the way to test a system is by trying to input different data into the
system to see whether it will accept the acceptable data and reject the
unacceptable data.
• The tested data falls under four categories:
❖Normal data
❖Extreme data
❖Abnormal data
❖Live Data
Normal Data

• Data that should be accepted and pass the test without a problem.
Extreme Data

• Data which is the border of what the system will accept.


Abnormal Data

• Data that should not be accepted by the system.


Live Data

• Finally, testing should be carried out using live data.


• Is used to test the system after it has been installed into
the environment.
• Data that is actually used in the real situation.
• Live data will be then compared with those produced from
the existing system.

You might also like