I was trying to get PHPUnit to give me some coverage report for a project I had not worked on for a long time. I had received a github pull request from someone and I wanted to see what the coverage was on the project to see if the submitter had done a good job of covering his code, but I couldn't get PHPUnit to generate a report that contained any data. All I would get was a couple of empty directory folders pages, which was useless.
I had code coverage work on another project in the same environment I was in, so I was pretty sure that my problem had to do either with how I had setup PHPUnit for that particular project, or that something else was interfering with the report generation.
I tried a couple of things, starting by calling phpunit from the command line using different arguments:
--coverage-html report test\symbol_test.php
Would generate some report with data in it, good!
-c test\phpunit.xml (logging set in phpunit.xml)
Would generate an empty report, not good...
--coverage-html report -c test\phpunit.xml
Would generate an empty report, not good...
So at that point I saw that it was working correctly and that something was definitely wrong with my phpunit.xml configuration file. I went back to the phpunit.de manual, specifically on the configuration page, and tried to figure out my problem.
For code coverage to be included in your report, you have to add a filter, be it a blacklist or a whitelist, but you have to have a filter.
So I quickly added a filter such as
which would whitelist everything that is in the project (my project root is one level above test). Ran phpunit in the test folder and I finally got a report with data!
A friend of mine was trying to install PHPUnit on his mac (OS X Lion), but unfortunately, he got stuck during the process.
At some point, he was faced with this error being displayed. We both looked at the problem and first made sure that said file existed. It was the case, weird...
A bit of googling will reveal that this is frequently fixed by appending the path to the pear folder to your php include_path (defined in your php.ini). But in his case, that was already done and it still wasn't working.
Next up was to check permissions problem. Not having read permissions on the file would of been an easy one to fix, but again, this was not the cause of the problem.
At this point you might be asking yourself, how come the file exists, you have permission to read it, but yet, you can't...
Well, the actual problem was that his OS was set up such that the maxfiles was set to 256 and PHPUnit had already reached that amount of open files.
To check if you have the same problem, try running phpunit using
sudo dtruss -f -t open phpunit (Linux users will want to use
strace -e open phpunit). In your output, you should see the files being opened. At some point, you'll find
Err#24, which indicates "To many file descriptors opened". If you have this problem, then the following should help you fix it.
The solution to this problem is quite easy. What you'll want to do is increase the maximum number of descriptors that can be used by a process. You can do it temporarily with
ulimit -S -n 1024 (to use 1024 instead of 256). Another way is to edit it and keep those settings (until you change them again) is to use
launchctl limit maxfiles 1024 unlimited.
I've been using PHPUnit recently to test a Kohana application I'm developing as my last semester project for my bachelor's degree.
At some point during the development, code coverage generation decided to stop working on my desktop (my remote CI still had no problem).
I started diagnosing the problem, being on Windows, I thought it could be due to the "poor job" I had done on installing php, pear and phpunit. I didn't want to go through the trouble or reinstalling everything though and just did the minimum: uninstall and reinstall phpunit. No success at that point.
I decided to go back a week or two in my SVN revisions, have it generate code coverage and get to the point were code coverage generation would fail. Took around 2 SVN "update to" to get to that point. After that, I tried updating the tests, but the new tests were using new features. So I updated the code first, then started updating the test files one by one. After a couple of files, I hit an interesting message:
ErrorException [ 1 ]: Allowed memory size of 134217728 bytes exhausted (tried to allocate 543278 bytes) ~ C:\php\pear\Text\Template.php [ 134 ]
I never had that message show up before, which is kind of strange. I would have expected PHP to tell me that same message everytime it tried to generate the documentation but couldn't...
So, quick fix was for me to edit my php.ini so that the memory_limit = 256M instead of 128M.