uuid: - value: 7281f569-60d5-45bd-8f3c-b01762098f77 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:36+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 as communication created: - value: '2023-07-20T00:00:00+00:00' changed: - value: '2025-05-11T09:00:36+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2023/07/20/tests-as-communication langcode: en body: - value: |

Automated tests aren't just checks to verify your software is working.

They're a communication tool that shows people working on the code how it's supposed to be used.

It's a form of documentation.

They are living examples of how to use the code with the benefit that you can run them and see if they still work, which isn't the case for markdown files or other types of static documentation that can become outdated.

Something I often do when evaluating or using software that has a test suite is review the tests and see how it's supposed to be used.

format: full_html processed: |

Automated tests aren't just checks to verify your software is working.

They're a communication tool that shows people working on the code how it's supposed to be used.

It's a form of documentation.

They are living examples of how to use the code with the benefit that you can run them and see if they still work, which isn't the case for markdown files or other types of static documentation that can become outdated.

Something I often do when evaluating or using software that has a test suite is review the tests and see how it's supposed to be used.

summary: null field_daily_email_cta: { }