Hi, 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. Regards.
If possible I'd like to receive any tips / tutorials about module creation and testing methodologies.
This list is for Drupal development. Your question is for the support list. But for some simple answers see http://lmgtfy.com/?q=tutorials+module+creation+drupal and http://lmgtfy.com/?q=drupal+testing F
Hi Fred, Since I am trying to develop/extend modules to be used within Drupal I thought that belonged here since I am not asking about installation or usage of an existing Drupal site. But I'll read on the results that came with your searches anyway. Regards. On Sun, Mar 6, 2011 at 1:30 AM, Fred Jones <fredthejonester@gmail.com>wrote:
If possible I'd like to receive any tips / tutorials about module creation and testing methodologies.
This list is for Drupal development. Your question is for the support list.
But for some simple answers see
http://lmgtfy.com/?q=tutorials+module+creation+drupal
and
http://lmgtfy.com/?q=drupal+testing
F
It is very much a development question, since it goes to the heart of the "deployment" problem in Drupal. Support is how to use Drupal. 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. In order to answer Robert's question, we need to honestly state the problem and help give the solution. Problem: read carefully the "deployment" section in Eaton's great essay: http://angrylittletree.com/11/01/drupal-8-road-ahead <http://angrylittletree.com/11/01/drupal-8-road-ahead>Solution: Read the articles in the bibliography to my article http://awebfactory.com.ar/node/458 If you are interested in my own thoughts you can read my article. There are three approaches to everything in code workflow (which is what you need): * 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)) * 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). * Use the deploy module with a features based approach. 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. Welcome to the community, Robert, once you choose your workflow, you will be able to arrive at a process you are comfortable with. Victor Kane http://awebfactory.com.ar http://projectflowandtracker.com On Sun, Mar 6, 2011 at 1:20 AM, robert mena <robert.mena@gmail.com> wrote:
Hi,
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.
Regards.
Hi Victor, I am already reading the blog posts mentioned. As a new developer to any "platform" I have a lot of questions specially how this or that can be done or applied to solve the problem. Right now I am in a process of actually deciding which would be the best way, going with drupal or symfony2. And for best way I mean understanding what each approach can bring as pros and cons. I hope this won't offend the other members of this list. On Sun, Mar 6, 2011 at 5:41 AM, Victor Kane <victorkane@gmail.com> wrote:
It is very much a development question, since it goes to the heart of the "deployment" problem in Drupal.
Support is how to use Drupal.
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.
In order to answer Robert's question, we need to honestly state the problem and help give the solution.
Problem: read carefully the "deployment" section in Eaton's great essay: http://angrylittletree.com/11/01/drupal-8-road-ahead
<http://angrylittletree.com/11/01/drupal-8-road-ahead>Solution: Read the articles in the bibliography to my article http://awebfactory.com.ar/node/458 If you are interested in my own thoughts you can read my article.
There are three approaches to everything in code workflow (which is what you need):
* 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)) * 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). * Use the deploy module with a features based approach.
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.
Welcome to the community, Robert, once you choose your workflow, you will be able to arrive at a process you are comfortable with.
Victor Kane http://awebfactory.com.ar http://projectflowandtracker.com
On Sun, Mar 6, 2011 at 1:20 AM, robert mena <robert.mena@gmail.com> wrote:
Hi,
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.
Regards.
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. Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr. ________________________________ From: robert mena <robert.mena@gmail.com> To: development@drupal.org Sent: Sat, March 5, 2011 11:20:43 PM Subject: [development] Tips for a new developer Hi, 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. Regards.
Hi Nancy, 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@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.
*Nancy*
Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
------------------------------ *From:* robert mena <robert.mena@gmail.com> *To:* development@drupal.org *Sent:* Sat, March 5, 2011 11:20:43 PM *Subject:* [development] Tips for a new developer
Hi,
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.
Regards.
participants (4)
-
Fred Jones -
nan wich -
robert mena -
Victor Kane