I also like the diagram in GOOS, page 42, where the authors add an additional step, right after "write a failing test": "Make the diagnostics clear."
On Mon, Nov 25, 2019 at 4:11 AM Roy Osherove <
roy@...> wrote:
Yup!
On Thu, Nov 14, 2019 at 6:05 AM Avi Kessner <
akessner@...> wrote:
Is this the diagram you wanted to share?
I would recommend making a box which is part of the flow rather than some external dotted lines. For example, maybe the box should read, " Apply SOLID principles" as part of the refactoring, and then before the next failing test have something like, "design the contract"
I think the community needs more explicit direction on the design being done in those phases.
On Tue, Nov 12, 2019 at 11:27 AM Roy Osherove <
roy@...> wrote:
?
Awesome.? I sent a new thread to the group about tdd diagrams.? Was it received?
Maybe.
If you sent it to the Yahoo! group, then no.
Please try again--at least until we figure out the transition. :) I want to see it!
--
J. B. (Joe) Rainsberger :: :: ::
--
