Concept: Developer Testing |
Developers test their code on a continuous basis to ensure that it works as expected and ensure the quality delivery.
Relationships
Related Elements | Developer Developer Testing How to Adopt the Evolutionary Design Practice Implement the Solution Implement Unit Tests Writing Unit Tests
Main Description
Developer testing is the act of testing of the source code by developers to ensure quality. It requires testing the code as it's written, and testing units or components to make sure they work well as a unit after the code has been completed. This occurs before complex system testing and integration to reveal errors earlier when they're easier to fix. Why Developer Testing? Developer testing is the means to Test a small unit of a project without waiting for the other parts to be completed. Test and fix problems simultaneously by multiple engineers. Detect and remove defects as soon as they're introduced. at a much less cost compared to other later stages of testing. Take advantage of formal testing techniques. Test internal conditions that are not easily reached by external inputs in the larger integrated systems (for example, exception conditions not easily reached in normal operation). Achieve a high level of structural coverage of the code,. Avoid lengthy compile-build-debug cycles when debugging difficult problems Testing Principles Find defects. Test early and often. The cost of change rises exponentially the longer it takes to find and then remove a defect. Build confidence. Many people fear making a change to their code because they are afraid that they will break it, Objectively measure quality. One test is worth a thousand opinions. You can say that your application works, but until you show the test results others might not believe. Test to the risk. The riskier something is, the more it needs to be reviewed and tested.
More Information
Concepts | Stubs
Examples | Stubs
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.