Abstract
It’s easy to look at a program module and say, “There, that’s finished,” but this sense of completion can be deceptive. How do you know for sure that the code completes all the use case scenarios—not just the basic courses, but the alternate courses, too?
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2007 Doug Rosenberg and Matt Stephens
About this chapter
Cite this chapter
(2007). Design-Driven Testing. In: Use Case Driven Object Modeling with UML. Apress. https://doi.org/10.1007/978-1-4302-0369-8_12
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0369-8_12
Publisher Name: Apress
Print ISBN: 978-1-59059-774-3
Online ISBN: 978-1-4302-0369-8
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books