And Now Letâs Write Some Rails
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]). In our case, weâre our own client and weâre working on a small project, so we donât exactly need military-grade precision. Hereâs my informal list of the first few things weâll tackle:
-
A user can create a project and seed it with initial tasks using the somewhat contrived syntax of task name:size.
-
A user can enter a task, associate it with a project, and see it on the project page. ...
Get Rails 4 Test Prescriptions 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.