Term
|
Definition
UNIT Testing is defined as a type of software testing where individual units/ components of a software are tested.
Unit Testing of software applications is done during the development (coding) of an application. The objective of Unit Testing is to isolate a section of code and verify its correctness. In procedural programming, a unit may be an individual function or procedure. Unit Testing is usually performed by the developer.
In SDLC, STLC, V Model, Unit testing is first level of testing done before integration testing. Unit testing is a WhiteBox testing technique that is usually performed by the developer. Though, in a practical world due to time crunch or reluctance of developers to tests, QA engineers also do unit testing. |
|
|
Term
|
Definition
Sometimes software developers attempt to save time by doing minimal unit testing. This is a myth because skipping on unit testing leads to higher Defect fixing costs during System Testing, Integration Testing and even Beta Testing after the application is completed. Proper unit testing done during the development stage saves both time and money in the end. Here, are key reasons to perform unit testing.
[image]
1.Unit Tests fix bug early in development cycle and save costs.
2.It helps understand the developers the code base and enable them to make changes quickly
3.Good unit tests serve as project documentation
4.Unit tests help with code re-use. Migrate both your code and your tests to your new project. Tweak the code till the tests run again. |
|
|
Term
|
Definition
Unit Testing is of two types
Manual
Automated
Unit testing is commonly automated but may still be performed manually. Software Engineering does not favor one over the other but automation is preferred. A manual approach to unit testing may employ a step-by-step instructional document. |
|
|
Term
|
Definition
Statement Coverage
Decision Coverage
Branch Coverage
Condition Coverage
Finite State Machine Coverage |
|
|
