From 9903fdf9dcd08e5980eeb83c2cfc4e130d96b988 Mon Sep 17 00:00:00 2001 From: mo Date: Tue, 4 Jun 2019 21:33:42 -0600 Subject: remove chit chat about TDD --- src/Q1/README.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/src/Q1/README.md b/src/Q1/README.md index f30290b..a2f59f0 100644 --- a/src/Q1/README.md +++ b/src/Q1/README.md @@ -161,15 +161,13 @@ Bye I started implementing this exercise by creating a class that matches the supplied class diagram in the assignment. I then started writing -testing using `junit` to flush out the expected API. I enjoy practicing -test driven development so writing my tests first helps me to explore -the target code from the perspective of the client and makes it easier -to refactor the code as I learn new techniques or optimizations. +testing using `junit` to flush out the expected API. +This makes it easier to refactor the code as I learn new techniques or optimizations. I only wrote happy path tests using `junit`, but this was enough to put together a running console application. I prefer to automate things as much as I can, so I chose to use maven -to create the default folder structure and some maven plugins to run -junit and a plugin to automatically format the code as per the Google +to create the default folder structure and used some maven plugins to run +`junit` and a plugin to automatically format the code as per the Google java code style guidelines. -- cgit v1.2.3