On Mon, Sep 24, 2012 at 5:07 PM, Daevid Vincent <daevid@xxxxxxxxxx> wrote: > That is a good point. We do not do unit tests here. Nothing against them, it’s just a bit overkill for our needs. We build lots of websites, not one massive SaaS. > > But I’m not saying do not use OOP. I’m just saying not everything has to be OOP. It’s a subtle but significant difference. > We have OOP classes for our database connection (and of course the helper routines), memecache access/purging/etc., and then objects for actors, movies, scenes, search results, HTML templates, email, tickets, etc… again, use the right tool for the job. When all you have is a hammer, everything is a nail. Build a toolbox. ;-) > > From: AmirBehzad Eslami [mailto:behzad.eslami@xxxxxxxxx] > Sent: Monday, September 24, 2012 12:47 PM > To: Daevid Vincent > Cc: PHP General Mailing List > Subject: Re: Joining a team, where no wiki or docs are available > > Wow. David. That was a great help with every detail ! > Thanks for sharing that with us. > > One side question: > Without OOP, how do you handle Unit Tests? > Do you know a Testing framework for procedural code? Wait, what? Unit testing has been around longer than OOP.... There weren't the nifty frameworks that make unit testing classes so much fun today, but you know you can *still* use them on procedural code. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
