Remove split, use excerpt block
This commit is contained in:
parent
aaa72e2186
commit
0858c7b6d5
10 changed files with 36 additions and 12 deletions
|
@ -14,11 +14,13 @@ meta:
|
|||
height: 1440
|
||||
type: image/png
|
||||
---
|
||||
{% block excerpt %}
|
||||
<p class="text-center" markdown="1"></p>
|
||||
|
||||
I recently gave a [talk on automated testing in Drupal][0] talk at [DrupalCamp Dublin][1] and as a lunch and learn session for my colleagues at Microserve. As part of the talk, I gave an example of how to build a Drupal 8 module using a test driven approach. I’ve released the [module code on GitHub][2], and this post outlines the steps of the process.
|
||||
<!-- split -->
|
||||
{% endblock %}
|
||||
|
||||
{% block content %}
|
||||
## Prerequisites
|
||||
|
||||
You have created a `core/phpunit.xml` file based on `core/phpunit.xml.dist`, and populated it with your database credentials so that PHPUnit can bootstrap the Drupal database as part of the tests. [Here is an example][5].
|
||||
|
@ -574,6 +576,7 @@ They all pass, so we be confident that the code works as expected, we can contin
|
|||
## Next Steps
|
||||
|
||||
I’ve started looking into whether some of the tests can be rewritten as kernel tests, which should result in quicker test execution. I will post any updated code to the [GitHub repository][3], and will also do another blog post highlighting the differences between functional and kernel tests and the steps taken to do the conversion.
|
||||
{% endblock %}
|
||||
|
||||
[0]: {{site.url}}/talks/tdd-test-driven-drupal
|
||||
[1]: http://2017.drupal.ie
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue