Change old /archive/* links to /daily/*
This commit is contained in:
parent
661669f2a5
commit
538141466c
406 changed files with 457 additions and 457 deletions
|
@ -3,7 +3,7 @@ title: >
|
|||
A breakdown of tests from a current project
|
||||
pubDate: 2023-10-07
|
||||
permalink: >-
|
||||
archive/2023/10/07/a-breakdown-of-tests-from-a-current-project
|
||||
daily/2023/10/07/a-breakdown-of-tests-from-a-current-project
|
||||
tags:
|
||||
- software-development
|
||||
- automated-testing
|
||||
|
@ -12,7 +12,7 @@ tags:
|
|||
|
||||
I've just added the hundredth test to a client project I'm developing.
|
||||
|
||||
I'm following [the outside-in approach]({{site.url}}/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.
|
||||
I'm following [the outside-in approach]({{site.url}}/daily/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:
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue