17 lines
1.7 KiB
Markdown
17 lines
1.7 KiB
Markdown
---
|
||
title: Test driven Drupal development with SimpleTest and PHPUnit
|
||
location: DrupalCamp London 2017
|
||
logo: assets/images/talks/logos/drupalcamp-london-2017.png
|
||
logo_link: http://drupalcamp.london/session/test-driven-drupal-development-simpletest-and-phpunit
|
||
slides: https://speakerdeck.com/opdavies/test-driven-drupal-development-with-simpletest-and-phpunit-drupalcamp-london-2017
|
||
slides_embed: <script async class="speakerdeck-embed" data-id="4f12722ed400468b93ebb32a23b3c757" data-ratio="1.37081659973226" src="//speakerdeck.com/assets/embed.js"></script>
|
||
tags: [drupalcamp, simpletest, phpunit, testing]
|
||
events:
|
||
- { title: DrupalCamp London 2017, date: 2017-03-05 }
|
||
---
|
||
Testing is important. Why? It allows developers to add new features and edit and 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 8 also includes and supports PHPUnit - the defacto PHP testing framework, used by other PHP projects including Symfony and Laravel - making it easier for people to test their code. And with testing being one of the Drupal core gates with tests needing to be included with every new feature or bug fix, and core’s 100% pass rate policy, testing has become an essential skill when contributing to core, or when working on your own projects.
|
||
|
||
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 module.
|