Navigation
User login
Pssst Hey You ... Yeah You ... Why aren't you contributing?
Thu, 03/13/2008 - 11:00am — Kevin
[ begin rant ]
A few days ago I posted to the planet about an initiative underway to help get testing in place for core and I must say I am not entirely impressed by the response from the community. Take that with a grain of salt though because, naturally, the Drupal Community Rocks.
Here's the synopsis:
A) There is an organization of volunteers in place poised and ready to write the simpletests we need.
B) The only reason, that I see, they are not doing this is lack of feedback from the Drupal community.
All that you have to do is edit the wiki page at http://groups.drupal.org/node/9625 ... it's only 4 core modules we are all familiar with ... a few moments of your time. We've even taken the liberty of contributing the first set of scenarios that need testing as an example. Take a look at it ... even adding one line will help Drupal. I won't even start bugging you about contributing to the testing initiative regularly ... at least not yet.
What are you waiting for? Drupal needs you.
[ end rant ]
Comments
Speaking as a developer who
Speaking as a developer who uses Drupal a lot, has developed a fair number of custom modules and a theme or two, but hasn't done much more than submit an occasional patch to core, I think the main thing for me is that I have no idea what any of this is about or why it's important--at least not without clicking your links and links from those links to synthesize that information together. And it appears to be about suggesting unit tests for a few core modules? I'm assuming for Drupal 7, right? The ones listed on the linked page aren't ones I use, and I haven't done anything with Drupal 7 (or even 6 yet; yeah, I'm slow) so I wouldn't feel qualified to suggest tests anyway. Like I said, I develop for Drupal and consider myself part of the "Drupal Community", but I don't hack on core and/or developing versions of Drupal much.
I guess what I'm saying is that if you can be more specific about who can realistically contribute (or what you'd need to do to be able to realistically contribute, e.g. run drupal 7 in a testing environment or whatever) and why it's such a big win (e.g. if we get these tests coded, we'll be able to release sooner or whatever), then I think you might get a better response. Anyway, I do hope you get what you're hoping for.
My $.02 :)
Great points ... Here's the
Great points ... Here's the short version until I make blog post getting more detailed. Dries announced that if we can provide continuous automated testing for Drupal core then the code freeze for D7 will be extended by 4 months. A good portion of the infrastructure to support this vision is already in place at http://testing.drupal.org/ ... but we are missing the tests necessary to completely cover Drupal core. If we come together as a community and provide the testing coverage needed then D7 benefits immensely. I'll follow up with another planet posting.
I respond well to rants
and put in the first few suggested tests for the taxonomy module...
benjamin, Agaric Design Collective
I'm trying
I actually had some suggestions to make, but http://groups.drupal.org/node/9625/edit is whitepaging right now.
So I'll try here. These are supposed to be unit tests, right? The first test for Node is:
Create, edit, and delete a node. Assure that the operations were successful. Before delete, check that the rss.xml contains the new node and that the new node is on the home page (i.e. test the /node callback).
Shouldn't create, edit, and delete each be a separate test? I think there is sufficiently different logic behind each event to make it its own unit.
AFAIK the answer to the "
AFAIK the answer to the " These are supposed to be unit tests, right?" is yes
Post new comment