uuid: - value: ee874ddb-dd03-4843-8a61-202936b2a845 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: | The best solution is the one that gets the tests to pass created: - value: '2023-10-04T00: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/10/04/the-best-solution-is-the-one-that-gets-the-tests-to-pass langcode: en body: - value: |
As I said yesterday, there is no perfect solution or approach for every situation.
However, when doing test-driven development, there is a best solution.
The simplest thing that gets a failing test to pass.
Whether it's hard-coding a return value or putting the initial logic in a Controller, that's the objective.
Once the test is passing, you can refactor the code or continue writing tests, which will each have their own best solution.
format: full_html processed: |As I said yesterday, there is no perfect solution or approach for every situation.
However, when doing test-driven development, there is a best solution.
The simplest thing that gets a failing test to pass.
Whether it's hard-coding a return value or putting the initial logic in a Controller, that's the objective.
Once the test is passing, you can refactor the code or continue writing tests, which will each have their own best solution.
summary: null field_daily_email_cta: { }