Hi Nancy,<div><br></div><div>Thanks for the reply.</div><div><br></div><div>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.</div>
<div><br></div><div>It avoids or helps detecting errors from being introduced and to make sure your code implements the required business rules.</div><div><br></div><div>At least that has been the case for me.<br><br><div class="gmail_quote">
On Sun, Mar 6, 2011 at 8:34 AM, nan wich <span dir="ltr"><<a href="mailto:nan_wich@bellsouth.net">nan_wich@bellsouth.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div style="font-family:arial, helvetica, sans-serif;font-size:12pt"><div></div>
<div>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.<br>
</div>
<p><font color="#ff007f" size="4" face="bookman old style, new york, times, serif"><em><strong>Nancy</strong></em></font></p>
<p> </p>
<p><font face="arial, helvetica, sans-serif">Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.</font></p>
<div><br></div>
<div style="font-family:arial, helvetica, sans-serif;font-size:12pt"><br>
<div style="font-family:times new roman, new york, times, serif;font-size:12pt"><font size="2" face="Tahoma">
<hr size="1">
<b><span style="font-weight:bold">From:</span></b> robert mena <<a href="mailto:robert.mena@gmail.com" target="_blank">robert.mena@gmail.com</a>><br><b><span style="font-weight:bold">To:</span></b> <a href="mailto:development@drupal.org" target="_blank">development@drupal.org</a><br>
<b><span style="font-weight:bold">Sent:</span></b> Sat, March 5, 2011 11:20:43 PM<br><b><span style="font-weight:bold">Subject:</span></b> [development] Tips for a new developer<br></font><div><div></div><div class="h5"><br>
Hi,
<div><br></div>
<div>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.</div>
<div><br></div>
<div>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.</div>
<div><br></div>
<div>If possible I'd like to receive any tips / tutorials about module creation and testing methodologies.</div>
<div><br></div>
<div>Regards.</div></div></div></div></div></div></div></blockquote></div><br></div>