Drupal Bristol Testing Workshop
Warning: This post is over a year old. I don't always update old posts with new information, so some of this information may be out of date.
Yesterday evening, I did my first workshop (and I believe, the first workshop) held at the Drupal Bristol user group. The subject was automated testing with PHPUnit in Drupal 8, in preparation for my talk at Drupal Developer Days 2018 next week and to help process some ideas for my testing book.
Here are some details about what we covered, and some of my thoughts in review.
Before the meetup, I set up a repository on GitHub that contains a Composer-based Drupal 8 installation, based on the Drupal 8 Composer template along with the Examples module (which includes some PHPUnit tests) with a pre-configured Docksal environment to use locally - Docksal being our standard local development environment that we use at Microserve for all of our projects, so something that I’m familiar with using.
In addition to the default stack, I added the PHPUnit add-on that I wrote so that it was easier to run tests, configured settings.php using environment variables and added a custom
fin init command to install the Composer dependencies and install Drupal. This meant after that installing Docksal, everyone had a running Drupal 8 website after only running
git clone and
fin init, and could then run tests straight away using
fin phpunit web/modules/contrib/examples/phpunit_example.
Once everyone was set up, we moved on to talk about why testing is important and the different options available to run them, before looking at the different types of tests available in Drupal 8. For each test type, I explained what it was used for and everyone completed an exercise on each - creating a test of that type, initially seeing it fail, and then doing the work to get it to pass.
The completed code that I wrote beforehand for these is available in their own GitHub repository, including all of the tests as well as the implementation code.
Once these exercises were completed, we looked at creating a blog page using test driven development - the example that I use in the TDD - Test Driven Drupal talk, to give a more real-word scenario. It would have been good to have gone through this as an exercise too, if we’d have had more time.
To finish, I demonstrated the PHPUnit integration within PHPStorm (which is working with Docksal) and showed some of the tests that I wrote for the Private Message Queue and System User modules, to see how things like adding items to queues and processing them, ensuring that emails are sent, to the right users and contain the right data, can be tested, as well as some of the tests that we’ve written on my work project over the last few months.
I didn’t record this workshop, but I have exported the slides and embedded them below:
I was very happy with how my first workshop went, it was a great experience for me and it seemed that the attendees all learnt something and found it interesting.
A couple of people mentioned about providing handouts to refer the code examples whilst working on the exercises, rather than relying on the slides and avoiding the need to sometimes switch back and forth between slides. I’ve found that I can export the slide deck as PNGs or JPGs from Deckset, so I’ll definitely do that next time.
I’m giving the Test Driven Drupal talk at the Drupal Dev Days conference next week, and I’m hoping to give it again at other meetups and events in the UK. If you’d like me to do either at your meetup or event, get in touch.
Questions? Comments? I’m @opdavies on Twitter.
About the Author
Oliver Davies is a Full Stack Web Developer and System Administrator based in the UK. He is a Senior Software Engineer and Technical Team Lead at Inviqa and a part-time freelancer specialising in Drupal, Symfony and Laravel development and Linux systems administration.