http://blog.shupp.org/2010/02/21/pragmatic-tips-for-unit-testing-in-php/ Software engineer, musician, space enthusiast Sat, 04 Feb 2012 23:40:29 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://blog.shupp.org/2010/02/21/pragmatic-tips-for-unit-testing-in-php/comment-page-1/#comment-606 Better code quality through easy access to tools « Bill Shupp Mon, 04 Apr 2011 03:46:11 +0000 http://blog.shupp.org/?p=51#comment-606 [...] unit tests and checking code coverage, profiling, and having links to documentation.  Though I've talked previously about the cost of maintaining 100% code coverage, I'm convinced that it's worth it if you not only [...] [...] unit tests and checking code coverage, profiling, and having links to documentation.  Though I've talked previously about the cost of maintaining 100% code coverage, I'm convinced that it's worth it if you not only [...]

]]> http://blog.shupp.org/2010/02/21/pragmatic-tips-for-unit-testing-in-php/comment-page-1/#comment-4 Rich Schumacher Mon, 22 Feb 2010 17:29:33 +0000 http://blog.shupp.org/?p=51#comment-4 One thing I've been trying to focus on is one of the bullet points from The Pragmatic Programmer: Find Bugs Once. If you find and fix a bug make sure there is a unit test that covers the case. You'll save yourself some time and frustration in the future. One thing I’ve been trying to focus on is one of the bullet points from The Pragmatic Programmer: Find Bugs Once. If you find and fix a bug make sure there is a unit test that covers the case. You’ll save yourself some time and frustration in the future.

]]>