uuid:
  - value: 0001428e-621c-49ca-83d3-4323ea446f48
langcode:
  - value: en
type:
  - target_id: daily_email
    target_type: node_type
    target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
revision_timestamp:
  - value: '2025-05-11T09:00:01+00:00'
revision_uid:
  - target_type: user
    target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
revision_log: {  }
status:
  - value: true
uid:
  - target_type: user
    target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
title:
  - value: "Tests aren't a line item"
created:
  - value: '2025-02-23T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:01+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2025/02/23/line-item
    langcode: en
body:
  - value: |
      <p>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.</p>

      <p>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.</p>

      <p>This is something I've always avoided.</p>

      <p>When broken out this way, it implies the automated tests are optional when they should be an integral part of the development process.</p>

      <p>They aren't a separate task that can be removed or skipped to save time or money.</p>

      <p>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.</p>

      <p>I want to know how much the whole task will cost and how long it will take.</p>

      <p>I assume they automatically test and verify the work they do and follow their industry's standard and best practices.</p>

      <p>I'm doing the same when developing software.</p>

              
    format: full_html
    processed: |
      <p>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.</p>

      <p>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.</p>

      <p>This is something I've always avoided.</p>

      <p>When broken out this way, it implies the automated tests are optional when they should be an integral part of the development process.</p>

      <p>They aren't a separate task that can be removed or skipped to save time or money.</p>

      <p>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.</p>

      <p>I want to know how much the whole task will cost and how long it will take.</p>

      <p>I assume they automatically test and verify the work they do and follow their industry's standard and best practices.</p>

      <p>I'm doing the same when developing software.</p>

              
    summary: null
field_daily_email_cta: {  }