Appendix A. Other Issues
“This sentence contradicts itself—or rather—well, no, actually it doesn’t!”
Douglas Hofstadter
We’re done with acceptance testing. No, not really. Here are a few more issues that didn’t seem to fit in the other chapters.
Context
When developing Sam’s system, the requirements and tests—check-out and check-in—were created first. The existence of CDs and customers were a given. Those tests form a context for other requirements and tests. Because entities such as CDs and customers are needed, there is an implicit requirement for a means to get them into the system.1 The existence of those entities implies that we probably need Create-Read-Update-Delete (CRUD) functionality for each of them, as shown in Chapter 12, “Development ...
Get Lean-Agile Acceptance Test-Driven Development: Better Software Through Collaboration 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.
