daily-email: add 2023-05-05
This commit is contained in:
parent
0302859cb0
commit
104396d773
19
src/content/daily-email/2023-05-05.md
Normal file
19
src/content/daily-email/2023-05-05.md
Normal file
|
@ -0,0 +1,19 @@
|
|||
---
|
||||
title: >
|
||||
Getting to green
|
||||
pubDate: 2023-05-05
|
||||
permalink: >
|
||||
archive/2023/05/05/getting-to-green
|
||||
tags:
|
||||
- automated-testing
|
||||
- testing
|
||||
- test-driven development
|
||||
---
|
||||
|
||||
When doing test-driven development, once you've written a failing (a.k.a. red) test, the main objective is to get to a green (a.k.a. passing) test as quickly as possible via the simplest method.
|
||||
|
||||
Even if that means returning a hard-coded value.
|
||||
|
||||
Once the test passes, it or the code it's testing can be refactored.
|
||||
|
||||
Or you can move on to the next test and, if you need to change the hard-coded value to get both tests to pass, then it is the right time to do so.
|
Loading…
Reference in a new issue