89 lines
3.6 KiB
YAML
89 lines
3.6 KiB
YAML
uuid:
|
|
- value: 5c687659-3110-4757-b25f-ab28a7190da5
|
|
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: |
|
|
A breakdown of tests from a current project
|
|
created:
|
|
- value: '2023-10-07T00: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/07/a-breakdown-of-tests-from-a-current-project
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>I've just added the hundredth test to a client project I'm developing.</p>
|
|
|
|
<p>I'm following <a href="/daily/2023/09/14/outside-in-or-inside-out">the outside-in approach</a>, starting with functional tests and moving to kernel and unit tests where needed - meaning more functional tests and fewer unit tests - most of which cover some complex search functionality containing custom blocks, forms, endpoints for autocomplete lists, pattern matching and results pages, which is the core functionality of the project.</p>
|
|
|
|
<p>Here's the breakdown of the different types of tests:</p>
|
|
|
|
<ul>
|
|
<li>Functional - 57 tests, 180 assertions</li>
|
|
<li>Kernel - 38 tests, 495 assertions</li>
|
|
<li>Unit - 5 tests, 18 assertions</li>
|
|
</ul>
|
|
|
|
<p>The tests are run automatically in a CI pipeline by GitHub Actions and Docker and usually run in two or three minutes.</p>
|
|
|
|
<p>The project is still in progress, so I'll add more tests for the remaining functionality and possibly remove some too, as I refactor some of the code.</p>
|
|
|
|
<hr />
|
|
|
|
<p>P.S. Are you interested in automated testing and test-driven development? I'm speaking about it at DrupalCon Europe on the 17th of October!</p>
|
|
|
|
<p>You can also pre-register for my free 10-day automated testing email course at https://opdavi.es/testing-email-course.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>I've just added the hundredth test to a client project I'm developing.</p>
|
|
|
|
<p>I'm following <a href="/daily/2023/09/14/outside-in-or-inside-out">the outside-in approach</a>, starting with functional tests and moving to kernel and unit tests where needed - meaning more functional tests and fewer unit tests - most of which cover some complex search functionality containing custom blocks, forms, endpoints for autocomplete lists, pattern matching and results pages, which is the core functionality of the project.</p>
|
|
|
|
<p>Here's the breakdown of the different types of tests:</p>
|
|
|
|
<ul>
|
|
<li>Functional - 57 tests, 180 assertions</li>
|
|
<li>Kernel - 38 tests, 495 assertions</li>
|
|
<li>Unit - 5 tests, 18 assertions</li>
|
|
</ul>
|
|
|
|
<p>The tests are run automatically in a CI pipeline by GitHub Actions and Docker and usually run in two or three minutes.</p>
|
|
|
|
<p>The project is still in progress, so I'll add more tests for the remaining functionality and possibly remove some too, as I refactor some of the code.</p>
|
|
|
|
<hr>
|
|
|
|
<p>P.S. Are you interested in automated testing and test-driven development? I'm speaking about it at DrupalCon Europe on the 17th of October!</p>
|
|
|
|
<p>You can also pre-register for my free 10-day automated testing email course at https://opdavi.es/testing-email-course.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|