Abstract
Testing is considered as integral to every phase of the OO lifecycle to ensure a well-developed test suite covering requirements, design and structure. Release criteria between the phases of development incorporate test-suite addition and documentation, allowing traceability from requirements through coding to specific test cases. Software engineers can pool their knowledge via the test suite, and the shared expertise can be used for regression testing after system alteration or for reuse considerations. The article also discusses the aspect of domain holes occurring within classes allowing the hiding of faults or flaws in the code.
| Original language | English |
|---|---|
| Pages (from-to) | 36-44 |
| Number of pages | 6 |
| Journal | Journal of Object Oriented Programming |
| Volume | 11 |
| Issue number | 9 |
| Publication status | Published - Feb 1999 |