Component Testing is a type of software testing in which usability of each individual component is tested. Along with the usability test, behavioral evaluation is also done for each individual component. To perform this type of testing, each component needs to be in independent state and also should be in controllable state. Each component of the software should be user comprehensible.
Assume in a software application consists of five components. The testing of each component is done independently by the tester as part of the development cycle before integration testing is performed on it. It helps in saving time by finding the bugs at a very early stage in the cycle. Test structure tools or debugging tools are used for this type of testing as this is performed by programmers on the code written by them and with the support of IDE. Defects detected during component testing are fixed as soon as possible when they are found without maintaining the records.
Component testing has an important role in finding the issue. Before processing with the integration testing, component testing is performed in order to ensure that each component of the application is working correctly and as per requirement.
Objective of Component Testing:
The objective of Component Testing is:
- To verify the input and output behavior of the system.
- To check the usability of each component.
- To test the user comprehensibility of the software.
- To test the state of the each components of the system.
Component Testing Process:
- Requirement Analysis:
User requirement related to each component is observed.
- Test Planning:
Test is planned according to the analysis of the requirements of the user.
- Test Specification:
In this section it is specified that which test case must be run and which test case should be skipped.
- Test Execution:
Once the test cases are specified according to the user requirements, test cases are executed.
- Test Recording:
Test recording is the having record of the defects that are detected.
- Test Verification:
Test verification is the process to determine whether the product meet specification.
This is the last phase of the testing process in which the result is analyzed.
- Difference between Component and Unit Testing
- Software Engineering | Differences between Sanity Testing and Smoke Testing
- Software Engineering | Comparison between Regression Testing and Re-Testing
- Software Testing | Reliability Testing
- Acceptance Testing | Software Testing
- Software Testing | Penetration Testing
- Software Testing | Scalability Testing
- Software Testing | Configuration Testing
- Software Testing | Functional Testing
- Software Testing | Scenario Testing
- Software Testing | Use Case Testing
- Software Testing | Manual Testing
- Software Testing | Security Testing
- Software Testing | Spike Testing
- Software Testing | Database Testing
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.