uuid: - value: de3c8e29-8a94-4f29-8c6a-267c0739c5c8 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:44+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: | Getting to green created: - value: '2023-05-05T00:00:00+00:00' changed: - value: '2025-05-11T09:00:44+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2023/05/05/getting-to-green langcode: en body: - value: |

When doing test-driven development, once you've written a failing (a.k.a. red) test, the main objective is to get to a green (a.k.a. passing) test as quickly as possible via the simplest method.

Even if that means returning a hard-coded value.

Once the test passes, it or the code it's testing can be refactored.

Or you can move on to the next test and, if you need to change the hard-coded value to get both tests to pass, then it is the right time to do so.

format: full_html processed: |

When doing test-driven development, once you've written a failing (a.k.a. red) test, the main objective is to get to a green (a.k.a. passing) test as quickly as possible via the simplest method.

Even if that means returning a hard-coded value.

Once the test passes, it or the code it's testing can be refactored.

Or you can move on to the next test and, if you need to change the hard-coded value to get both tests to pass, then it is the right time to do so.

summary: null field_daily_email_cta: { }