On the Facile.it Engineering blog there's a recent post sharing some tips on how to gradually upgrade your PHPUnit tests to work with version 6 of the popular PHP unit testing tool.

In the latest months I wrote multiple times, in different projects, code migrating PHPUnit toward major version 6. This upgrade is harder than the previous one, since in this version it was introduced a big breaking change: all classes got (finally!) namespaced.

This means that any usage of those classes in your project needs to be updated. [...] In this article I will explain which steps I applied during those migrations, highlighting the most frequent hiccups.

He then start with "the easy one" to take care of the refactor: updating tests to replace the "PHPUnit_*" classes with the namespaced versions. With those out of the way, he talks about "the bumpy one" to handle: modifying test listeners to work with the new PHPUnit structure. Once these are taken care of you can then make the move up to PHPUnit 6 and PHP 7 (if you're not there already) full time.

On thePHP.cc site there's a new post sharing what you need to know about migrating your PHPUnit installation up to PHPUnit 6 from previous versions.

The first version of PHPUnit 6 was released today. Today also marks the End of Life of PHPUnit 4. What does this mean for you? The answer to this question depends on which versions of PHP and PHPUnit you currently use.

They break the reminder of the article down into three sections:

• what you'll need to change to update from PHPUnit 4
• what you'll need to change to update from PHPUnit 5
• what kinds of things come with PHPUnit 6 that "you'll want to use"

This last section includes updates like the changes to namespacing, having "risky" test checking enabled by default, deprecated APIs and the ability to export a log file JUnit will understand.