daily-email: fix post
This commit is contained in:
parent
2ec8a49de5
commit
2f7d260601
|
@ -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.
|
||||
|
|
Loading…
Reference in a new issue