Skip to main content

Unit Testing

Unit Testing is the smallest testable part of the software.  It may be a function, Class, procedure and the Interface. In Unit Testing individual unit of source code are tested to determine whether they are fit for use.

Unit Testing is the short source code testing which is done by programmer or done by white box tester during the development process. This testing mode is component of Extreme Programming (XP), which means developing a product with continuous testing and revisions.



In the Unit Testing, developer think only about the unit which is under test. If any error occur then they fix it as per the Unit without thinking about the effect over other unit. Once every unit fix or error free then on integration we concern about the effects.

Unit Testing finds problem early in the development phase. These bugs may be because of the flow that development are using or any missing part in the specification. The cost of finding the bugs in Unit Testing phase is lower if bugs found in later stages so Unit Testing is very important phase of Testing as per the cost.

Unit Testing allow the programmer to upgrade system in later stage means unit testing allow the user to change the code if needed. Unit Testing make the system less interdependent so the changes on one unit reduces the error in other units.

Unit Testing simplifies the Integration Testing. It uses the bottom up testing approach. First tested the Unit and them complete modules so possibility of errors is reduces.

Unit Testing is the part of documentation. Developer look at the document and as per the document write the code.


Comments

Popular posts from this blog

What is API?

In general way, API (Application Programming Interface) is the intermediate software which is useful for two applications to communicate. API is the tool which is used for interaction of two applications. If developer developing any software which have multiple blocks (Modules) than developer use APIs to put them together.

Smoke Testing

In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.

Difference between Error, Bug, Defect and Failure

Error: Any mistake in the coding called error. The mistake may be Syntax error, Logical errors or other GUI errors lead errors in any software. These are from developer side. Defect: The error which made by developer and during testing, Tester is able to find that errors,  means if actual result deviated from expected result then that error called defects. This is caught by testers. Bug: The defect which is developed by tester team, if expected by the developer team then that defect called an bug. Failure: If the Software does not meet the client requirement then this is called failure of the software.