This paper is an overview of software unit testing. It defines unit testing, and discusses many of the issues, which must be addressed when planning for unit testing. It also makes suggestions for appropriate levels of formality and thoroughness of unit testing. Software unit testing is an integral part of an efficient and effective strategy for testing systems. The designer of the code under test best performs it. The appropriate level of formality and thoroughness of the testing will vary from project to project, and even within a project depending on the criticality, complexity, and risk associated with the unit. The policy in this regard should be decided early in test planning, and documented, usually in the Project Plan or separate Master Test Plan. In most cases it is acceptable to adopt an approach which requires little documentation overhead. However there are some basic requirements which should always be met. In particular it must be reviewable, repeatable, and archivable. Commonly, unit testing will be recorded in lab books, or in hand-written notes on code listings stored in the project journal, with guidance provided by a checklist that identifies the required unit testing activities.
Did you find this white paper useful?
31 out of 50 users found this white paper useful
Related white papers
White paper: The Future of Software Delivery
This paper provides a brief description of past software delivery issues that have contributed to the current environment; identification of key trends that drive our industry today; and an outline...
Podcast: Building the James Webb Space Telescope
When the Webb Telescope takes off for its perch in space, it will be operated by some 200,000 lines of software code. Since a system failure would involve a...
Outsourcing Testing – An overview
With competitive pressures compelling software development firms to cut costs and reduce time-to-market, there is a growing trend among developers to outsource their application testing processes to offshore IT service...
IBM Rational ClearCase VOB Troubleshooting
IBM Rational ClearCase VOBs use a proprietary database format, the Raima database. Troubleshooting VOB databases can be difficult. This white paper describes how to troubleshoot ClearCase VOB database problems and...
On Guard: Producing Run-Time Checks From Integrity Constraints
Software applications are inevitably concerned with data integrity, whether the data is stored in a database, files, or program memory. An integrity guard is code executed before a data update...
WebEx Builds Interactive Media Platform Using Forte Developer 6
WebEx is the leader in real-time communications infrastructure for Web meetings. WebEx built a service that could handle massive concurrent connections while maintaining exceptional response times to support live video,...
3-D Look at the IBM Software Development Platform for Linux
This webcast explains how the IBM Software Development Platform supports development teams in a Linux environment. This event covers the 3-D aspect of the IBM SDP for Linux: Discovery, Development...
