uuid:
  - value: 6bd02fde-eab4-4c41-8808-e9f1c00f85d3
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:05+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: 'Run your tests more often'
created:
  - value: '2024-11-04T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:05+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2024/11/04/run-your-tests-more-often
    langcode: en
body:
  - value: |
      <p>There's no value in a test suite that isn't run and the less often it's run, the less likely you are to spot a failure or regression.</p>

      <p>If the tests are only run weekly, you aren't going to be aware of an issue that could have been introduced at the start of the week until the tests are run.</p>

      <p>Then, there are more changes that need to be reviewed to find the cause of the issue compared to if it was found sooner.</p>

      <p>Ideally, everyone should be running tests locally as well as having them run automatically in a CI pipeline for each commit.</p>

      <p>As soon as a failing commit is pushed, it will be identified and it will be easy to fix or revert.</p>

      <p>Also, the more often you push changes and in smaller batches - the easier it will be to diagnose and resolve the issue.</p>

              
    format: full_html
    processed: |
      <p>There's no value in a test suite that isn't run and the less often it's run, the less likely you are to spot a failure or regression.</p>

      <p>If the tests are only run weekly, you aren't going to be aware of an issue that could have been introduced at the start of the week until the tests are run.</p>

      <p>Then, there are more changes that need to be reviewed to find the cause of the issue compared to if it was found sooner.</p>

      <p>Ideally, everyone should be running tests locally as well as having them run automatically in a CI pipeline for each commit.</p>

      <p>As soon as a failing commit is pushed, it will be identified and it will be easy to fix or revert.</p>

      <p>Also, the more often you push changes and in smaller batches - the easier it will be to diagnose and resolve the issue.</p>

              
    summary: null
field_daily_email_cta: {  }