Code coverage results can give a false sense of quality. With the
@coversNothing annotations, you can better express the intention of your test. This leads to better code coverage results that truly reflect the coverage of your tests.
This article explains how you can require a package from a local path into your project with Composer. This way you can run a local copy of a repository and test any changes you make. Because the local repo will be symlinked changes are shared in real-time, there is no need for intermediate committing and updating.
When you start a new project it is best to stick the best practices. Skeleton projects provide a good basis. I'll describe how to get up and running fast.
This is a quick tip on how to get code coverage results when running PHPUnit on Laravel Homestead. This will enable Xdebug first and then run your tests.
In this post, I give an overview of my second day at Laracon EU 2017. I'll describe the presentations I've seen and things that stood out for me.
This is a report of my first day at Laracon EU 2017. I'll describe the talks I saw and what stood out for me.
Lately, I've been working on a project that has to read data from an MSSQL database. This is the setup that we used to connect to the database and solve any encoding issues.
Last week I published my first open source package. This is what I learned while working on it.
This post explains how you can create and configure a custom module for Codeception. This is the easiest way to extend on Codeception in a reusable way.
Codeception is normally configured using the codeception.yml file. We can also use a dotenv configuration file to store any sensitive data. This posts shows you how.