You are reading the article What Is Component Testing? Techniques, Example Test Cases updated in September 2023 on the website Speedmintonvn.com. We hope that the information we have shared is helpful to you. If you find the content interesting and meaningful, please share it with your friends and continue to follow and support us for the latest updates. Suggested October 2023 What Is Component Testing? Techniques, Example Test CasesWhat is Component Testing?
Component testing is defined as a software testing type, in which the testing is performed on each individual component separately without integrating with other components. It’s also referred to as Module Testing when it is viewed from an architecture perspective. Component Testing is also referred to as Unit Testing, Program Testing or Module Testing.
Generally, any software as a whole is made of several components. Component Level Testing deals with testing these components individually.
It’s one of most frequent black box testing types which is performed by QA Team.
The usage of the term “Component Testing” varies from domain to domain and organization to organization.
The most common reason for different perception of Component testing are
Type of Development Life Cycle Model Chosen
Complexity of the software or application under test
Testing with or without isolation from rest of other component in software or application.
As we know Software Test Life Cycle Architecture has lots many test-artifacts (Documents made, used during testing activities). Among many tests – artifacts, it’s the Test Policy & Test Strategy which defines the types of testing, depth of testing to be performed in a given project.Who does Component Testing
Component testing is performed by testers. ‘Unit Testing’ is performed by the developers where they do the testing of the individual functionality or procedure. After Unit Testing is performed, the next testing is component testing. Component testing is done by the testers.When to perform Component testing
Component testing is performed soon after the Unit Testing is done by the developers and the build is released for the testing team. This build is referred as UT build (Unit Testing Build). Major functionality of all the components are tested in this phase,
Entry criteria for component testing
Minimum number of the component to be included in the UT should be developed & unit tested.
Exit criteria for component testing
The functionality of all the component should be working fine.
There should not presence of any Critical or High or Medium severity & priority defects Defect log.Component Testing Techniques
Based on depth of testing levels, Component testing can be categorized as
CTIS – Component Testing In Small
CTIL – Component Testing In Large
CTIS – Component Testing in Small
Component testing may be done with or without isolation of rest of other components in the software or application under test. If it’s performed with the isolation of other component, then it’s referred as Component Testing in Small.
Example 1: Consider a website which has 5 different web pages then testing each webpage separately & with the isolation of other components is referred as Component testing in Small.
Example 2: Consider the home page of the chúng tôi website which has many components like
Home, Testing, SAP, Web, Must Learn!, Big Data, Live Projects, Blog and etc.
Similarly, any software is made of many components and also, every component will have its own subcomponents. Testing each modules mentioned in example 2 separately without considering integration with other components is referred as Component Testing in Small.
How to do Component Testing
Note: The sub-component are mentioned with red highlighted color in the below snapshot.
How to do Component Testing
CTIL – Component Testing in Large
Component testing done without isolation of other components in the software or application under test is referred as Component Testing Large.
Let’s take an example to understand it in a better way. Suppose there is an application consisting of three components say Component A, Component B, and Component C.
The developer has developed the component B and wants it tested. But in order to completely test the component B, few of its functionalities are dependent on component A and few on component C.
But the component A and component C has not been developed yet. In that case, to test the component B completely, we can replace the component A and component C by stub and drivers as required. So basically, component A & C are replaced by stub & driver’s which acts as a dummy object till they are actually developed.
Stub: A stub is called from the software component to be tested as shown in the diagram below ‘Stub’ is called by Component A.
Driver: A driver calls the component to be tested as shown in the diagram below ‘Component B’ is called by Driver.Example Test Cases for Component Testing
Consider 2 webpages as per the diagrams mentioned below, Here both the web page are interrelated to each other from a functionality point of view.
Web page 2 is home page of chúng tôi
So here login page is one component, and the home page is another. Now testing the functionality of individual pages separately is called component testing.
Component testing scenario’s on web page1 –
Enter invalid user id and verify if any user-friendly warning pop up is shown to the end user.
Component testing scenario’s on web page2 –
Verify if the “Welcome to manager page of guru99 bank” message is being displayed on the home page.
Verify if the manager id is being displayed in the center of the home page.
Verify the presence of the 3 different images on the home page as per the diagram.Unit Testing Vs Component Testing
Unit Testing Component Testing
Testing individual programs, modules to demonstrate that program executes as per the specification is called Unit Testing
Testing each object or parts of the software separately with or without isolation of other objects is called Component Testing
Its validated against design documents
Its validated against test requirements, use cases
Unit testing is done by Developers
Component testing is done by Testers
Unit testing is done first
Component testing is done after unit testing is complete from the developers end.Summary:
In Software Engineering, Component testing plays a crucial role in finding the bugs. Before we start the Integration Testing after the component testing and the integration testing is followed by component testing.
Component testing also referred as module testing in some references.
You're reading What Is Component Testing? Techniques, Example Test Cases
Update the detailed information about What Is Component Testing? Techniques, Example Test Cases on the Speedmintonvn.com website. We hope the article's content will meet your needs, and we will regularly update the information to provide you with the fastest and most accurate information. Have a great day!