Fix compile errors due to prettier changes
This commit is contained in:
parent
8092202ba8
commit
2b591083f0
|
@ -6,6 +6,7 @@ contact_email: 'oliver@testdrivendrupal.com'
|
||||||
|
|
||||||
{% block content %}
|
{% block content %}
|
||||||
|
|
||||||
|
<!-- prettier-ignore -->
|
||||||
<div class="markup spaced-y-4 mb-6" markdown="1">
|
<div class="markup spaced-y-4 mb-6" markdown="1">
|
||||||
Having [given talks][1] and workshops, been a guest on podcasts and [written articles][0] about automated testing in Drupal, I’m currently in the planning phase of a book and potentially some accompanying screencasts about it, focussing on Drupal 8.
|
Having [given talks][1] and workshops, been a guest on podcasts and [written articles][0] about automated testing in Drupal, I’m currently in the planning phase of a book and potentially some accompanying screencasts about it, focussing on Drupal 8.
|
||||||
|
|
||||||
|
@ -49,7 +50,10 @@ and be notified of any updates.**
|
||||||
|
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
{% include 'pages/book/signup-form' %} {% endblock %}
|
{% include 'pages/book/signup-form' %}
|
||||||
|
|
||||||
|
<!-- prettier-ignore -->
|
||||||
|
{% endblock %}
|
||||||
|
|
||||||
[0]: /articles/tags/testing
|
[0]: /articles/tags/testing
|
||||||
[1]: /talks/tdd-test-driven-drupal
|
[1]: /talks/tdd-test-driven-drupal
|
||||||
|
|
|
@ -37,11 +37,14 @@ events:
|
||||||
time: '14:00 - 14:45'
|
time: '14:00 - 14:45'
|
||||||
---
|
---
|
||||||
|
|
||||||
{% block content %} Testing is important. Why? It allows developers to add new
|
{% block content %}
|
||||||
features and edit and refactor existing code without the worry of adding
|
|
||||||
regressions, reduces the reliance on manual testing to discover bugs, and by
|
<!-- prettier-ignore -->
|
||||||
taking a test driven approach, your implementation code is leaner as you only
|
Testing is important. Why? It allows developers to add new features and edit and
|
||||||
write what is needed for your tests to pass.
|
refactor existing code without the worry of adding regressions, reduces the
|
||||||
|
reliance on manual testing to discover bugs, and by taking a test driven
|
||||||
|
approach, your implementation code is leaner as you only write what is needed
|
||||||
|
for your tests to pass.
|
||||||
|
|
||||||
Drupal 7 includes the SimpleTest module for unit and functional testing, whilst
|
Drupal 7 includes the SimpleTest module for unit and functional testing, whilst
|
||||||
Drupal 8 also includes and supports PHPUnit - the defacto PHP testing framework,
|
Drupal 8 also includes and supports PHPUnit - the defacto PHP testing framework,
|
||||||
|
@ -53,10 +56,14 @@ to core, or when working on your own projects.
|
||||||
|
|
||||||
In this talk, we’ll cover the methodology and terminology involved with
|
In this talk, we’ll cover the methodology and terminology involved with
|
||||||
automated testing, and then take a test driven approach to creating a new Drupal
|
automated testing, and then take a test driven approach to creating a new Drupal
|
||||||
module. {% endblock %}
|
module.
|
||||||
|
|
||||||
|
<!-- prettier-ignore -->
|
||||||
|
{% endblock %}
|
||||||
|
|
||||||
{% block tweets %}
|
{% block tweets %}
|
||||||
|
|
||||||
|
<!-- prettier-ignore -->
|
||||||
<div class="flex flex-wrap -mx-2">
|
<div class="flex flex-wrap -mx-2">
|
||||||
<div class="w-full sm:w-1/2 lg:w-1/3 px-2 flex flex-col">
|
<div class="w-full sm:w-1/2 lg:w-1/3 px-2 flex flex-col">
|
||||||
{% include 'tweet' with {
|
{% include 'tweet' with {
|
||||||
|
|
Reference in a new issue