30 lines
1.2 KiB
Markdown
30 lines
1.2 KiB
Markdown
|
---
|
||
|
title: Tests aren't a line item
|
||
|
date: 2025-02-23
|
||
|
permalink: daily/2025/02/23/line-item
|
||
|
tags:
|
||
|
- software-development
|
||
|
- automated-testing
|
||
|
cta: ~
|
||
|
snippet: |
|
||
|
Automated tests should be part of the software development process, not a separate line item.
|
||
|
---
|
||
|
|
||
|
A common mistake I see with new Developers and Development teams when starting with automated testing is to split development time and testing into separate tasks.
|
||
|
|
||
|
They'll say when quoting a client or in an estimation session that the development time will take x hours and writing tests will take y hours.
|
||
|
|
||
|
This is something I've always avoided.
|
||
|
|
||
|
When broken out this way, it implies the automated tests are optional when they should be an integral part of the development process.
|
||
|
|
||
|
They aren't a separate task that can be removed or skipped to save time or money.
|
||
|
|
||
|
If I take my car to a garage, I don't ask them how long it will take to repair and how long to test what they've done.
|
||
|
|
||
|
I want to know how much the whole task will cost and how long it will take.
|
||
|
|
||
|
I assume they automatically test and verify the work they do and follow their industry's standard and best practices.
|
||
|
|
||
|
I'm doing the same when developing software.
|