88 lines
2.8 KiB
YAML
88 lines
2.8 KiB
YAML
uuid:
|
|
- value: e88621ad-4a3d-481e-b292-b710f0756313
|
|
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:12+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 first test is the hardest'
|
|
created:
|
|
- value: '2024-05-16T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:12+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2024/05/16/the-first-test-is-the-hardest
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>Whether you're writing tests before the implementation code or not, the first test is always the hardest to write.</p>
|
|
|
|
<p>What will the arrange and act phases look like?</p>
|
|
|
|
<p>What dependencies will you need?</p>
|
|
|
|
<p>What do you need to mock or create fakes of?</p>
|
|
|
|
<p>In a Drupal test, what other modules and configuration do you need to install?</p>
|
|
|
|
<p>What installation profile and default theme do you need to use?</p>
|
|
|
|
<p>What other unknown or complicated setup steps are there?</p>
|
|
|
|
<p>Do you need to configure your environment to run the tests and get the expected output?</p>
|
|
|
|
<h2 id="here%27s-the-thing">Here's the thing</h2>
|
|
|
|
<p>The hardest part is getting the arrange/setup phase working and getting to when the test is running your business logic.</p>
|
|
|
|
<p>Once you've got the first test running, adding more for similar use cases will be much easier.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>Whether you're writing tests before the implementation code or not, the first test is always the hardest to write.</p>
|
|
|
|
<p>What will the arrange and act phases look like?</p>
|
|
|
|
<p>What dependencies will you need?</p>
|
|
|
|
<p>What do you need to mock or create fakes of?</p>
|
|
|
|
<p>In a Drupal test, what other modules and configuration do you need to install?</p>
|
|
|
|
<p>What installation profile and default theme do you need to use?</p>
|
|
|
|
<p>What other unknown or complicated setup steps are there?</p>
|
|
|
|
<p>Do you need to configure your environment to run the tests and get the expected output?</p>
|
|
|
|
<h2 id="here%27s-the-thing">Here's the thing</h2>
|
|
|
|
<p>The hardest part is getting the arrange/setup phase working and getting to when the test is running your business logic.</p>
|
|
|
|
<p>Once you've got the first test running, adding more for similar use cases will be much easier.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|