[development] Tips for a new developer
robert.mena at gmail.com
Sun Mar 6 15:36:33 UTC 2011
Thanks for the reply.
I beg to differ as long as we still have some independent Q&A team involved.
But for me creating your code to be easily tested (specially if automated)
is a must.
It avoids or helps detecting errors from being introduced and to make sure
your code implements the required business rules.
At least that has been the case for me.
On Sun, Mar 6, 2011 at 8:34 AM, nan wich <nan_wich at bellsouth.net> wrote:
> As a certified project manager as well as a Drupal developer, I see the TDD
> approach as flawed, particularly if the test and code developers are the
> same person, which the word "first" implies. In a more ideal situation, they
> would be done from a proper Design document - in parallel, by different
> people. But, in my experience, few Drupal development projects follow good
> methodologies unless done by larger contracting companies, so be prepared to
> throw any methodology you know out the window.
> Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L.
> King, Jr.
> *From:* robert mena <robert.mena at gmail.com>
> *To:* development at drupal.org
> *Sent:* Sat, March 5, 2011 11:20:43 PM
> *Subject:* [development] Tips for a new developer
> I am beginning to develop for drupal and plan to use it as my framework.
> I've been using Zend for a while so I am still trying to get used to the
> way things are done.
> So far I have some questions about strategies for development since I try
> to follow a TDD methodology (test driven development) where I develop the
> tests first and then go actually developing the code that performs the
> expected behavior.
> If possible I'd like to receive any tips / tutorials about module creation
> and testing methodologies.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development