TECHNOLOGY AND

LIVELIHOOD
EDUCATION
9
COMPUTER SYSTEMS SERVICING
Technology and Livelihood Education– Grade 9
Quarter 4 – Module 12: Testing Component
First Edition, 2020

Republic Act 8293, section 176 states that: No copyright shall subsist in any work
of the Government of the Philippines. However, prior approval of the government
agency or office wherein the work is created shall be necessary for exploitation of
such work for profit. Such agency or office may, among other things, impose as a
condition the payment of royalties.

Borrowed materials (i.e., songs, stories, poems, pictures, photos, brand names,
trademarks, etc.) included in this module are owned by their respective copyright
holders. Every effort has been exerted to locate and seek permission to use these
materials from their respective copyright owners. The publisher and authors do not
represent nor claim ownership over them.

Published by the Department of Education Division of Pasig City

Development Team of the Module

Writer: Ma. Gloria Lisette Gay R. Espinas
Editors: Maria O. del Barrio, Jhoanna V. Navata
Reviewers: Maria O. del Barrio, Jhoanna V. Navata

Illustrator: Edison P. Clef

Layout Artist:
Management Team: Ma. Evalou Concepcion A. Agustin
OIC-Schools Division Superintendent
Carolina T. Rivera, CESE
OIC-Assistant Schools Division Superintendent
Manuel A. Laguerta EdD
Chief, Curriculum Implementation Division
Victor M. Javeña EdD
Chief, School Governance and Operations Division and

Education Program Supervisors

Librada L. Agon EdD (EPP/TLE/TVL/TVE)
Liza A. Alvarez (Science/STEM/SSP)
Bernard R. Balitao (AP/HUMSS)
Joselito E. Calios (English/SPFL/GAS)
Norlyn D. Conde EdD (MAPEH/SPA/SPS/HOPE/A&D/Sports)
Wilma Q. Del Rosario (LRMS/ADM)
Ma. Teresita E. Herrera EdD (Filipino/GAS/Piling Larang)
Perlita M. Ignacio PhD (EsP)
Dulce O. Santos PhD (Kindergarten/MTB-MLE)
Teresita P. Tagulao EdD (Mathematics/ABM)

Printed in the Philippines by Department of Education – Schools Division of Pasig

City
 T. L. E. 9
COMPUTER SYSTEMS SERVICING

Quarter 4
Self-Learning Module 13
Testing Component
Introductory Message

For the facilitator:

Welcome to the Technology and Livelihood Education Module on Computer
Systems Servicing 9!
This module was collaboratively designed, developed and reviewed by
educators from Schools Division Office of Pasig City headed by its Officer-
In-Charge Schools Division Superintendent, Ma. Evalou Concepcion A.
Agustin in partnership with the Local Government of Pasig through mayor,
Honorable Victor Ma. Regis N. Sotto.
The writers utilized the standards set by the K to 12 Curriculum using the
Most Essential Learning Competencies (MELC) while overcoming their
personal, social, and economic constraints in schooling.
This learning material hopes to engage the learners into guided and
independent learning activities at their own pace and time. Further, this
also aims to help learners acquire the needed 21st century skills especially
the 5 Cs namely: Communication, Collaboration, Creativity, Critical
Thinking and Character while taking into consideration their needs and
circumstances.
In addition to the material in the main text, you will also see this box in the
body of the module:

Notes to the Teacher

This contains helpful tips or
strategies that will help you in
guiding the learners.

As a facilitator you are expected to orient the learners on how to use this
module. You also need to keep track of the learners' progress while
allowing them to manage their own learning. Moreover, you are expected
to encourage and assist the learners as they do the tasks included in the
module.
For the learner:
Welcome to the Technology and Livelihood Education Module on Computer
Systems Servicing!
The hand is one of the most symbolized part of the human body. It is often
used to depict skill, action and purpose. Through our hands we may learn,
create and accomplish. Hence, the hand in this learning resource signifies
that you as a learner is capable and empowered to successfully achieve the
relevant competencies and skills at your own pace and time. Your
academic success lies in your own hands!
This module was designed to provide you with fun and meaningful
opportunities for guided and independent learning at your own pace and
time. You will be enabled to process the contents of the learning material
while being an active learner.
This module has the following parts and corresponding icons:
Expectation - These are what you will be able to know after completing the
lessons in the module

Pre-test - This will measure your prior knowledge and the concepts to be
mastered throughout the lesson.

Recap - This section will measure what learnings and skills that you
understand from the previous lesson.

Lesson- This section will discuss the topic for this module.

Activities - This is a set of activities you will perform.

Wrap Up- This section summarizes the concepts and applications of the
lessons.
Valuing-this part will check the integration of values in the learning
competency.

Post-test - This will measure how much you have learned from the entire module.
 EXPECTATION
At the end of the lesson, the students should be able to:
A. define component testing;
B. describe the four levels of testing;
C. appreciate the importance of component testing.

PRETEST
Choose the letter of the correct answer.

1. It is the lowest unit of any application.

a. Bugs c. Drivers
b. Component d. Program

2. These values are used to determine how many test cases to construct.
a. Component Implementations
b. Component Specifications
c. Project Test Plan
d. System Requirements

3. It is used to determine which parts of a component should be tested more

than other parts.
a. Component Implementations
b. Component Specifications
c. Project Test Plan
d. System Requirements

4. This refers to constraints on their inputs and outputs, specific sequences

of operations and series of functional models.
a. Component Implementations
b. Component Specifications
c. Project Test Plan
d. System Requirements

5. It provides the information necessary to construct the structural and

interaction test cases.
a. Component Implementations
b. Component Specifications
c. Project Test Plan
d. System Requirements
 RECAP

Give the difference of the following:

1. Metadata ________________________________
2. Questionnaire ________________________________
3. Survey ________________________________

L E S S ON

Testing Component

The word component generally means a piece of something. In computer

hardware it refers to the motherboard, CPU, RAM and hard drive. In software, a
component is the lowest unit of any application. So, component testing is a method
of testing the lowest or the smallest unit of any application. It is sometimes referred
to as Program or Module Testing. An application can be considered of a
combination and integration of many small individual modules. Before we test the
entire system, it is essential that each component or the smallest unit of the
application is tested thoroughly.

In this case, the modules or the units are tested independently. Each module
receives an input, performs some processing and produces the output. The output
is then validated against the expected feature. The software applications are huge in
nature and it is a question to test the entire system. It may run into many gaps in
the test coverage. Before continuing into Integration testing or functional testing, it
is recommended to start with Component testing.

The main objective of component testing is to validate the input/output

behavior of the test object. It ensures that the test object’s functionality is working
correctly and totally fine as per the desired specification.

Component Testing is a sort of white box testing. It looks for bugs and
validates the functioning of the modules/programs which are individually testable.
Test strategy and test plan are needed for component testing. There is a test setting
for each component which are broken down in test cases. The following diagram
represents the process:
The four major inputs to component level testing are:

1. Project Test Plan - This plan will provide information such as the expected
levels of specification and code coverage. These values will be used to
determine how many test cases to construct.
2. System Requirements – It is a detailed and structured use case model
which can assist in determining the required behaviors for individual
domain-level classes sufficiently. The use case model is also used to create
the use profile to determine which parts of a component should be tested
more than other parts.
3. Component Specifications – In component specification, there are three
types of properties should be included from which the functional test cases
will be built.

a. Individual operations are specified in terms of limitations on their inputs

and outputs. These are indicated as pre and post-conditions.
b. The state of the object is restricted by a consistency that specifies limits on
each of the attributes of the object.
c. The interactions among methods and attributes are specified by a series of
functional models usually recorded using object interaction diagrams. This
limits how the methods implement the component’s attributes.

4. Component Implementations – Needed information are provided to

construct the structural and interaction test case during the actual
implementation of the design. The language used is an important factor in
the quality of the implementation for some types of faults are made
impossible by the language and new sets of faults are presented.

Component Testing is done by quality assurance services or the tester. In

component testing, it takes account of authenticating functional or specific non-
functional characteristics of system components like testing resource behavior (e.g.
looking for memory leaks), performance testing, structural testing, etc. This is done
after unit testing.

After creating the component, it immediately tested. There are chances that the
results retrieved from a component under test are dependent on other components
which in turn are not developed as of now. As to the development lifecycle model,
component testing may be performed separately from other components of the
system. The separation is done to prevent external influences. So, to test the
component, we use Stubs and Drivers for simulating the interface between software
components.

ACTIVITY

A. Describe the following levels of testing.

1. Project Test Plan

_________________________________________________________________________
_________________________________________________________________________

2. System Requirements
_________________________________________________________________________
_________________________________________________________________________

4. Component Specifications
________________________________________________________________________
________________________________________________________________________

5. Component Implementations
________________________________________________________________________
________________________________________________________________________

WRAP–UP

Illustrate the process of component testing through a graphic organizer.

 VALUING

Where can you apply today’s lesson in your everyday activities?

________________________________________________________________________
________________________________________________________________________

POST TEST

Directions: Write the word or group of words being describe.

1. It is the lowest unit of any application.

______________________________________

2. These values are used to determine how many test cases to construct.

______________________________________

3. It is used to determine which parts of a component should be tested more

than other parts.

______________________________________

4. This refers to constraints on their inputs and outputs, specific sequences

of operations and series of functional models.

_______________________________________

5. It provides the information necessary to construct the structural and

interaction test cases.

______________________________________

KEYTOCORRECTION
 COMPONENT IMPLEMENTATION 5. A 5.
COMPONENT SPECIFICATION 4. B 4.
SYSTEM REQUIREMENT 3. D 3.
PROJECT TEST PLAN 2. C 2.
COMPONENT 1. B 1.
POST TEST PRETEST

R E F E R E N CE S

A Component Testing Method. Accessed February 22, 2021.

https://people.cs.clemson.edu/~johnmc/joop/col5/column5.html.

Sharma, Lakshay. "What Is Unit/Component Testing in Software Testing?"

TOOLSQA. July 12, 2020. Accessed February 22, 2021.
https://www.toolsqa.com/software-testing/istqb/component-testing/

Shekhar, David (MBCS), Sindhu, Kimaya Sathi, Software Testing Books, Sree
Sudha, Nikita, Akash Bisht, Harsha K. M, Pranita, and Jerome. "What Is
Component Testing Or Module Testing (Learn With Examples)." Software
Testing Help. February 18, 2021. Accessed February 22, 2021.
https://www.softwaretestinghelp.com/what-is-component-testing-or-
module-testing/.