From 6a14b2542a6a17e831c3eed13101472498da1886 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Tue, 9 May 2023 23:38:59 +0100 Subject: [PATCH] daily-email: add 2023-05-07 --- src/content/daily-email/2023-05-07.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 src/content/daily-email/2023-05-07.md diff --git a/src/content/daily-email/2023-05-07.md b/src/content/daily-email/2023-05-07.md new file mode 100644 index 000000000..67d19a4c5 --- /dev/null +++ b/src/content/daily-email/2023-05-07.md @@ -0,0 +1,20 @@ +--- +title: > + You don't need to think about what to do next +pubDate: 2023-05-07 +permalink: > + archive/2023/05/07/you-don't-need-to-think-about-what-to-do-next +tags: + - automated-testing + - test-driven-development +--- + +When practising test-driven development, you don't need to think about what to do next. + +If you have a failing test, the objective is to get that test to pass as quickly and simply as possible, and you rely on the error from the failing test to tell you the next step. + +It could be a failing assertion, an undefined variable or function, or a yet-to-be-implemented service. + +Once you've fixed that error, the test will either pass or fail. If it fails, you'll have a new error and know the next step. + +When working in this way, it's like being on autopilot. You can focus only on fixing each error until the feature or fix is complete and the test is passing.