Chapter 16. Separating Tests with Use-Case Test Slices
So far in this part of the book, we have discussed how to drive different kinds of use cases from requirements to code. Testing is an integral part of this work and should not be perceived as a separate activity done at the end. In fact, design is not complete until you know how to test your design elements. Likewise, implementation (coding) is not complete until the actual tests pass. When testing each element, you often need to somehow control the execution of the element being tested to follow the execution path stipulated by the test scenario. You also need to instrument (i.e., check and collect information about) the execution to determine that the behavior of the element is indeed correct. ...
Get Aspect-Oriented Software Development with Use Cases 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.
