Quality assurance

A session is focusing on code quality control and goes from simple to more complicated:

1. Defining the types of problems of the code

2. Evaluating its risks: psychological, reputational, time-related

3. Looking at the tools available to evaluate the code against the problems defined: PHP Lint, PHP Code Sniffer, PHP Mess Detector

4. Covering Drupal specifics of the task

Automatic Drupal instances per Git branch under your control, on your own server or your Kubernetes cluster.

When working with a (remote) team and/or for your sprint review, it is essential that your colleagues, product owners or stakeholders can easily try out your software, that is, not only see, but also make use of what you have implemented. Preferably, this should be possible for each branch in your repository.