daily-email: add 2023-08-13
Don't estimate separately for testing
This commit is contained in:
parent
539edc0f54
commit
d083b7af8b
18
src/content/daily-email/2023-08-13.md
Normal file
18
src/content/daily-email/2023-08-13.md
Normal file
|
@ -0,0 +1,18 @@
|
|||
---
|
||||
title: >
|
||||
Don't estimate separately for testing
|
||||
pubDate: 2023-08-13
|
||||
permalink: >
|
||||
archive/2023/08/13/dont-estimate-separately-for-testing
|
||||
tags:
|
||||
- automated-testing
|
||||
- test-driven-development
|
||||
---
|
||||
|
||||
A common issue I see people introducing automated testing is estimating the testing and implementation of a task separately.
|
||||
|
||||
Something like, "It'll take x to do the work and x to write the tests for it".
|
||||
|
||||
As well as implying you'd write all the code and then all the tests or vice versa, if you provide separate estimates, it's easy for someone to think the tests are optional and can be removed.
|
||||
|
||||
If you provide one estimate for both, this can't happen.
|
Loading…
Reference in a new issue