uuid: - value: 2c83980a-deb6-4e52-95a8-a87155cc3e2a 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:30+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: | Automated testing offers repeatability created: - value: '2023-09-30T00:00:00+00:00' changed: - value: '2025-05-11T09:00:30+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2023/09/30/automated-testing-offers-repeatability langcode: en body: - value: |

You work on feature or bug fix.

It gets tested manually by you, a tester, and the person who requested the feature or reported the bug.

It may get tested on multiple environments.

It passes and it moved to production.

But now it's live, it's not tested again.

Although it works now, there's no guarantee it's not broken or regressed by subsequent changes.

It's definitely not tested manually before every future release.

Here's the thing

Automated testing offers repeatability.

The tests pass, so the functionality works when you wrote it, and you can re-check it by re-running the test.

The test suite can be run by Developers whilst working on other changes, before code review and before deployments.

The test suite can be run automatically in a CI pipeline for every change that's pushed, and you'll know your change not only worked at the time but will continue to work.

format: full_html processed: |

You work on feature or bug fix.

It gets tested manually by you, a tester, and the person who requested the feature or reported the bug.

It may get tested on multiple environments.

It passes and it moved to production.

But now it's live, it's not tested again.

Although it works now, there's no guarantee it's not broken or regressed by subsequent changes.

It's definitely not tested manually before every future release.

Here's the thing

Automated testing offers repeatability.

The tests pass, so the functionality works when you wrote it, and you can re-check it by re-running the test.

The test suite can be run by Developers whilst working on other changes, before code review and before deployments.

The test suite can be run automatically in a CI pipeline for every change that's pushed, and you'll know your change not only worked at the time but will continue to work.

summary: null field_daily_email_cta: { }