phpunit - Digital Craftsman

Digital Craftsman

Sign in Subscribe

phpunit

A collection of 14 posts

Overwrite APP_ENV in PHPUnit

Overwrite APP_ENV in PHPUnit

Important when you're using something like Docker where you inject the env variables directly into the environment rather than just pulling them from a .env file with a PHP dotenv component. Make sure to use force="true" in your phpunit.xml.dist like: <phpunit ...>

To many open files in PHPUnit

To many open files in PHPUnit

Running bigger projects with more moving components leads to more files being used at one time by the system. This is in issue for example when running PHPUnit. An error message you might get is: failed to open dir: Too many open files The amount of files you can have

Run only one test in PHPUnit

Run only one test in PHPUnit

While writing your tests, you of course don't want to run your whole test suite again and again to check if one tests runs through. There are ways to group tests with @group annotations and ways to run just one file by suppling the path to the file.

Mock object without mocking methods

Mock object without mocking methods

When mocking an object with PHPUnit, all methods are automatically also mocked. When you only want to cancel the constructor, but want the methods still to be used, you can define that with using null as parameter for setMethods. $handler = $this ->getMockBuilder('MyCustomHandler') ->disableOriginalConstructor(

A better mock object builder for PHPUnit

When working with mocks for unit tests, you're going to write a lot of code for the mocks. There are a lot of functions you're going to need to call every single time. To get around this you can use the following utility function[1]: /** * Get

Show PHPUnit details with TAP

TAP or Test Anything Protocol [http://testanything.org] (a simple text-based interface between testing modules) is also available for PHPUnit. You can use it to show details with the flag --tap: $ phpunit --tap Which will result in an output like the following: TAP version 13 ok 1 - newArrayIsEmptyTest(ArrayTest)

Testing an abstract class

With normal mocks it's possible to test functions with many dependencies. But in PHPUnit and mocks there is also a way to test abstract classes. We can use the PHPUnit_Framework_TestCase::getMockForAbstractClass() method for this: class FancyThing extends PHPUnit_Framework_TestCase { public function testAbstractThing() { $abstractThing = $this->

Testing private and protected methods with PHPUnit

It's easy to test public methods with PHPUnit. But what if you want to test protected or private methods? To test those you can use reflection to create a reflection method and invoke this method like the following: $method = new ReflectionMethod('FancyThing', 'doSomethingFancy'); $method-&

Don't throw "Exception" in PHP

There are a few classes in PHP which are better used for inheritance only. Exception is one of them. Of course you can use/throw it, but you can run into problems. For example you've got problems with PHPUnit. We're were running an older version of

Notifications from iTerm with content images

As an addition to the last Native OSX notifications from iTerm with Triggers [http://blog.liplex.de/native-osx-notifications-from-iterm-with-triggers/] article there is also a solution to add content images to the notifications. We use the parameter -contentImage of terminal-notifier to display the image. To make it easier we adjust the script

Native OSX notifications from iTerm with Triggers

As an addition to the last Show notification when PHPUnit tests are done in iTerm [http://blog.liplex.de/show-notification-for-finished-phpunit-tests-in-iterm/] article there is also a solution to fire notifications from iTerm on certain triggers with native OSX notifications (instead of Growl). To do this just install the terminal-notifier gem with[

Show notification when PHPUnit tests are done in iTerm

I've got a few thousand unit tests in a project which I run with PHPUnit. Running them can take quite a while. I run them through and ant command though the Mac app iTerm. Running them takes quite a while. There is a nice way to be notified

Show phpunit coverage

When running phpunit you have the option to show how much of your code is covered by tests and which parts aren't. To do this just run phpunit with the following flag: $ phpunit --coverage-html path/to/folder This command will create a documentation of your code coverage and

Stop phpunit tests on error

When writing tests it can happen, that one of the tests failes and all the others fail as result of it. Like for example when something in your EntityManager crashes (it's closed and can't be used in any of the following tests which leads to them