It is very much a development question, since it goes to the heart of the "deployment" problem in Drupal.<div><br></div><div>Support is how to use Drupal.<br><div><br></div><div>Robert is not asking how to actually write a module or how to run simple test. Robert is asking about how to set up a best practices workflow, specifically, TDD, in Drupal.</div>
<div><br></div><div>In order to answer Robert's question, we need to honestly state the problem and help give the solution.</div><div><br></div><div>Problem: read carefully the "deployment" section in Eaton's great essay: <meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://angrylittletree.com/11/01/drupal-8-road-ahead">http://angrylittletree.com/11/01/drupal-8-road-ahead</a></div>
<div><br></div><div><a href="http://angrylittletree.com/11/01/drupal-8-road-ahead"></a>Solution: Read the articles in the bibliography to my article <meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://awebfactory.com.ar/node/458">http://awebfactory.com.ar/node/458</a> If you are interested in my own thoughts you can read my article.</div>
<div><br></div><div>There are three approaches to everything in code workflow (which is what you need): </div><div><br></div><div>* Features module based approach, carefully taking into account the unadvertised pitfalls therein (see the funnymonkey articles for their statement of the problem and the solution; see the sachachua article for excellent ideas; see the nuvole article for excellent real world developer approaches also (they are going to present at DrupalCon on this))</div>
<div>* Write all your applications as installation profiles, then deploy content using the deploy module; use the everything in code bricks features relies upon (views in code, etc., even taxonomy in code).</div><div>* Use the deploy module with a features based approach.</div>
<div><br></div><div>The deploy module assigns UUID's to nodes, etc. in Drupal, and on that basis the deployment problem is solved, actually. Should be in core.</div><div><br></div><div>Welcome to the community, Robert, once you choose your workflow, you will be able to arrive at a process you are comfortable with.</div>
<div><br></div><div>Victor Kane</div><div><a href="http://awebfactory.com.ar">http://awebfactory.com.ar</a></div><div><a href="http://projectflowandtracker.com">http://projectflowandtracker.com</a></div><div><br><div class="gmail_quote">
On Sun, Mar 6, 2011 at 1:20 AM, robert mena <span dir="ltr"><<a href="mailto:robert.mena@gmail.com">robert.mena@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
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>
</blockquote></div><br></div></div>