addressalign-toparrow-leftarrow-leftarrow-right-10x10arrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcredit-cardcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobe--smallglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1languagelaunch-new-window--smalllight-bulblightning-boltlinklocation-pinlockm-swarmSearchmailmediummessagesminusmobilemoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstar-shapestartickettrashtriangle-downtriangle-uptwitteruserwarningyahooyoutube

Re: [mysql-144] Re: [TriPUG] Tripug: PHP Best Practices

From: Steve W.
Sent on: Monday, August 16, 2010, 2:24 PM 
There seems to be some debate on using PHPUnit for Unit testing and
Functional Testing.
PHPUnit looks interesting and there are some fine addons - like
coverage testing for larger projects.



On Mon, Aug 16, 2010 at 12:23 PM, Michael Kimsal <[address removed]> wrote:
> Some other 'best practices' (or perhaps just 'good practices').
>
>
> 1. ��Write unit and functional tests.
> 2. ��As Bryan said, use meaningful variable names.
> 3. ��Adopt a style and use it consistently (I still struggle with this a bit).
> 4. ��Use tabs, not spaces :)
> 5. ��Use phpdoc on your methods and functions.
>
> Any others you all want to contribute?
>

Raleigh, NC

Founded Mar 19, 2006

Organizers:

Michael Kimsal, Chris Gmyr, Emily Stamey
Contact

People in this
group are also in: