65 lines
2.3 KiB
YAML
65 lines
2.3 KiB
YAML
|
uuid:
|
||
|
|
- value: e91d28ca-1730-4560-82ab-205175ca2bf9
|
||
|
|
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:20+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: 'Start with a failing test'
|
||
|
|
created:
|
||
|
|
- value: '2024-02-01T00:00:00+00:00'
|
||
|
|
changed:
|
||
|
|
- value: '2025-05-11T09:00:20+00:00'
|
||
|
|
promote:
|
||
|
|
- value: false
|
||
|
|
sticky:
|
||
|
|
- value: false
|
||
|
|
default_langcode:
|
||
|
|
- value: true
|
||
|
|
revision_translation_affected:
|
||
|
|
- value: true
|
||
|
|
path:
|
||
|
|
- alias: /daily/2024/02/01/start-with-a-failing-test
|
||
|
|
langcode: en
|
||
|
|
body:
|
||
|
|
- value: |
|
||
|
|
<p>When fixing a bug or adding a new feature using test-driven development, it's important to see the test fail first.</p>
|
||
|
|
|
||
|
|
<p>You should write your test so it doesn't pass by default or accidentally.</p>
|
||
|
|
|
||
|
|
<p>When creating data, such as users or nodes within tests, do so in a way that will force the test to fail, such as explicitly setting the title or published date into a non-default order.</p>
|
||
|
|
|
||
|
|
<p>When fixing a bug, write a test that represents the expected outcome when the bug is fixed. This confirms the bug exists and can be replicated.</p>
|
||
|
|
|
||
|
|
<p>Then, once the tests pass, you know the feature or fix is working and that it's because of your changes and not for any other reason.</p>
|
||
|
|
|
||
|
|
|
||
|
|
format: full_html
|
||
|
|
processed: |
|
||
|
|
<p>When fixing a bug or adding a new feature using test-driven development, it's important to see the test fail first.</p>
|
||
|
|
|
||
|
|
<p>You should write your test so it doesn't pass by default or accidentally.</p>
|
||
|
|
|
||
|
|
<p>When creating data, such as users or nodes within tests, do so in a way that will force the test to fail, such as explicitly setting the title or published date into a non-default order.</p>
|
||
|
|
|
||
|
|
<p>When fixing a bug, write a test that represents the expected outcome when the bug is fixed. This confirms the bug exists and can be replicated.</p>
|
||
|
|
|
||
|
|
<p>Then, once the tests pass, you know the feature or fix is working and that it's because of your changes and not for any other reason.</p>
|
||
|
|
|
||
|
|
|
||
|
|
summary: null
|
||
|
|
field_daily_email_cta: { }
|