Unit Testing Best Practices

Unit Testing Best Practices
In software development projects, unit testing is a software program validation type in which the coder verifies every units of source code versus its specification. A unit is nothing but a most atomic testable part of a developed application program. In procedural computer programing one program, function, procedure, etc. can be considered as unit. In object-oriented computer programmings, the smallest unit is a method, which may lie in to a base/super class, abstract class or derived/child class.
Here are a few Better Practices:
1. The print out of a unit should reside on a single sheet of paper.
2. If there are more than 7 levels of nested unit, then maybe it should be break in more than two.
3. If the cyclomatic complexness of a unit is larger than 8 then it's getting excessively complex.
4. when it is content-coupled with another unit then it Is not a good unit.
The process is:
1. Prepare a test Plan of the unit tests.
2. Designing the tests, the test environment, and operator instructions.
3. Key Out and get the test data.
4. Code and run the tests.
5. Analyse the results.

For more information visit: Software Testing and the articles Unit Testing Best Practices

also check http://softwareqatestings.xanga.com/weblog