February 2018
Intermediate to advanced
406 pages
9h 52m
English
To start a test-driven development process, it’s important to have some requirements in mind. Without some sense of what your code should be doing, it’s hard to write tests to describe behavior.
Requirements-gathering could be an entire book by itself (specifically, this one: Software Requirements, 2nd Edition [Wie03]). For purposes of this example, let’s assume you’re your own client and you’re working on a small project, so you don’t exactly need military-grade precision. Here’s my informal list of the first few things you’ll tackle:
A user can enter a task, associate it with a project, and also see it on the project page.
A user can create a project and seed it with initial tasks using the somewhat contrived syntax ...