O'Reilly logo

Lean-Agile Acceptance Test-Driven Development: Better Software Through Collaboration by Ken Pugh

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

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 ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required