Testing Off-the-Shelf Components
Increasingly, functionality is added to an application by purchasing “chunks” of software referred to as components.[7] The quality of these components varies tremendously from one vendor to another. Until standardized measures are adopted or the marketplace forces improved quality, you should plan to do an acceptance test on any newly acquired component.
[7] Chapter 10 will cover topics about components, but this is a natural place to talk about them.
An acceptance test should put the component into the context in which it will be used. The test cases should thoroughly investigate the limits of the specification.[8] Creating the specification document will not be a wasted effort because developers will need it ...
Get A Practical Guide to Testing Object-Oriented Software now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
