From d083b7af8bc1d31d5a102d91eca254b4bfd02803 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Sun, 13 Aug 2023 20:51:00 +0100 Subject: [PATCH] daily-email: add 2023-08-13 Don't estimate separately for testing --- src/content/daily-email/2023-08-13.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 src/content/daily-email/2023-08-13.md diff --git a/src/content/daily-email/2023-08-13.md b/src/content/daily-email/2023-08-13.md new file mode 100644 index 00000000..fb62a7a5 --- /dev/null +++ b/src/content/daily-email/2023-08-13.md @@ -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.