From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Avdi Grimm" Subject: Re: Regression testing for org-mode Date: Thu, 23 Oct 2008 20:03:56 -0400 Message-ID: References: <4900A06B.8020605@sift.info> <87wsfyx3tp.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KtA9q-0006kD-Cz for emacs-orgmode@gnu.org; Thu, 23 Oct 2008 20:04:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KtA9o-0006k0-Ly for emacs-orgmode@gnu.org; Thu, 23 Oct 2008 20:04:01 -0400 Received: from [199.232.76.173] (port=38459 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KtA9o-0006jx-JW for emacs-orgmode@gnu.org; Thu, 23 Oct 2008 20:04:00 -0400 Received: from rv-out-0708.google.com ([209.85.198.241]:38341) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KtA9o-0007Pr-2x for emacs-orgmode@gnu.org; Thu, 23 Oct 2008 20:04:00 -0400 Received: by rv-out-0708.google.com with SMTP id k29so690097rvb.6 for ; Thu, 23 Oct 2008 17:03:56 -0700 (PDT) In-Reply-To: <87wsfyx3tp.fsf@gmail.com> Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Eric Schulte Cc: emacs-orgmode@gnu.org, Robert Goldman On Thu, Oct 23, 2008 at 7:57 PM, Eric Schulte wrote: > > I'm pessimistic that the colossal amount of work involved in wrapping > all of org-modes extensive and varied functionality into a test > framework can/should actually be completed. Would it be sufficient to > simply begin dealing with bug reports in a test-first manner? Absolutely. I do NOT recommend making an effort to get test coverage over existing code just for the sake of coverage - in my experience this usually leads a lot of work for brittle and not terribly useful tests. Put tests only around the areas you are about to change. Over time the coverage will grow. > Also, should we start tracking bug reports somewhere (worg), so that > they can be claimed, tested against, and repaired? Not a bad idea. Normally I'd recommend just going with an established bug tracker like Trac or Lighthouse, but since Org is so great for managing tasks it seems only right that the developers should "eat their own dogfood" by using Org to track tickets :-) -- Avdi Home: http://avdi.org Developer Blog: http://avdi.org/devblog/ Twitter: http://twitter.com/avdi Journal: http://avdi.livejournal.com