uuid:
  - value: f6a3faae-6a4e-478d-9a81-95fb87ab7d47
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:32+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: |
      Including time for tests in estimates
created:
  - value: '2023-09-03T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:32+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2023/09/03/including-time-for-tests-in-estimates
    langcode: en
body:
  - value: |
      <p>If you need to provide estimates for your tasks and intend to write tests, include the time for the tests within the estimate.</p>

      <p>Don't provide different estimates for testing and the implementation, or with tests and without tests - give one estimate that includes both.</p>

      <p>Writing tests and testable code will take longer to begin with, but practice makes perfect and will save time in the long run.</p>

              
    format: full_html
    processed: |
      <p>If you need to provide estimates for your tasks and intend to write tests, include the time for the tests within the estimate.</p>

      <p>Don't provide different estimates for testing and the implementation, or with tests and without tests - give one estimate that includes both.</p>

      <p>Writing tests and testable code will take longer to begin with, but practice makes perfect and will save time in the long run.</p>

              
    summary: null
field_daily_email_cta: {  }