From 2f7d2606015dfcb12bf611a36e61fff88b0e6e3c Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Thu, 12 Oct 2023 00:34:30 +0100 Subject: [PATCH] daily-email: fix post --- src/content/daily-email/2023-10-07.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/daily-email/2023-10-07.md b/src/content/daily-email/2023-10-07.md index f6a33769..9921ca82 100644 --- a/src/content/daily-email/2023-10-07.md +++ b/src/content/daily-email/2023-10-07.md @@ -10,7 +10,9 @@ tags: - test-driven-development --- +I've just added the hundredth test to a client project I'm developing. +I'm following [the outside-in approach](https://www.oliverdavies.uk/archive/2023/09/14/outside-in-or-inside-out), starting with functional tests and moving to kernel and unit tests where needed - meaning more functional tests and fewer unit tests - most of which cover some complex search functionality containing custom blocks, forms, endpoints for autocomplete lists, pattern matching and results pages, which is the core functionality of the project. Here's the breakdown of the different types of tests: @@ -18,8 +20,6 @@ Here's the breakdown of the different types of tests: * Kernel - 38 tests, 495 assertions * Unit - 5 tests, 18 assertions -I'm following [the outside-in approach](https://www.oliverdavies.uk/archive/2023/09/14/outside-in-or-inside-out), starting with functional tests and moving to kernel and unit tests where needed - meaning more functional tests and fewer unit tests - most of which cover some complex search functionality containing custom blocks, forms, endpoints for autocomplete lists, pattern matching and results pages, which is the core functionality of the project. - The tests are run automatically in a CI pipeline by GitHub Actions and Docker and usually run in two or three minutes. The project is still in progress, so I'll add more tests for the remaining functionality and possibly remove some too, as I refactor some of the code.