The short answer is no.
The long answer is no, and you should avoid writing static methods altogether. Static methods making testing harder. You may not be at the point where you are testing your code (you should start immediately) but the least you can do to help your self right now is to stop writing static method. Hard Stop. No exceptions.
I realize creating an instance just to use a method that has no state seems like extra typing, but in the long run it will pay off.
Some support for why static methods suck:
http://googletesting.blogspot.com/2008/12/static-methods-are-death-to-testability.html
http://www.giorgiosironi.com/2009/11/mocking-static-methods-road-to-hell.html
It's not testing the method itself that causes the problem, its when you are testing other classes and methods that rely on other static methods--forcing you to usually set up a ton of context to get all the other static things to work so you can test the current method you care about. It is much easier to mock your dependencies so you can test the subject directly.
If you need a resource to get into testing, heres one (there are many!). http://www.sitepoint.com/tutorial-introduction-to-unit-testing-in-php-with-phpunit/