Component or Unit Testing

Component (modular) testing verifies the functionality and looks for defects in parts of the application that are available and can be tested separately ( program modules, objects, classes, functions, etc. ). Usually component (modular) testing is performed by calling code that needs to be verified with the support of development environments such as frameworks for modular testing or debugging tools. All defects found are usually corrected in the code without their formal description in the Bug Tracking System.

One of the most effective approaches to component (unit) testing is the preparation of automated tests prior to the start of basic coding (development) of software. This is called test-driven development or a test first approach . With this approach, small pieces of code are created and integrated, opposite which tests run before the start of encoding are run. Development is carried out until all tests are successfully passed.

The difference between component and unit testing

In essence, these levels of testing represent the same thing, the only difference is that in component testing, real objects and drivers are used as parameters of functions, and specific values ​​are used in the unit testing.

See also

• Unit testing
• Mobile testing
• Web testing
• Types and types of testing. Testing levels
• Methods to ensure the high quality of the developed software