Monday, March 10, 2008

Dries' newly released Usability Testing first results (here) are in, and it does reinforce my previous point that even as we make the code and patch testing better (via unit tests), many other parts of quality have been overlooked for some time, and developers shouldn't be the ones to force it on. (you can read that previous post here)

In fact, between this and some valuable feedback I received from those in #drupal, I've decided to outline a full proposal for moving Drupal's Quality Assurance forward. As Karoly was kind enough to mention, just posting about this on my development blog isn't enough :) . I'm writing that proposal now, and will be posting it in the Quality Assurance group at sometime tomorrow.

I should also note that contrary to some feedback I received from #drupal, I do think unit testing is a great thing, and I do think Drupal is doing good, and I do think we're making progress (one of the (very) few downsides of open source communities is that people take criticism very personally, since everyone who works on Drupal does in a way feel it's a bit of them ;) ) I was, in no way, saying that anyone wasn't doing their jobs, just that we hadn't recognized some of these QA areas as even being needed before. Alright, enough apologizing, I'll see you all tomorrow!

(If there is anything you think the proposal should include, give me a heads up)

No comments: