Don't estimate separately for testing

A common issue I see for 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.

- Oliver

Was this interesting?

Sign up here and get more like this delivered straight to your inbox every day.

About me

Picture of Oliver

I'm an Acquia-certified Drupal Triple Expert with 17 years of experience, an open-source software maintainer and Drupal core contributor, public speaker, live streamer, and host of the Beyond Blocks podcast.