From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Rose Subject: Re: How you can help Date: Thu, 23 Oct 2008 19:33:55 +0200 Message-ID: <877i7z9px8.fsf@kassiopeya.MSHEIMNETZ> References: <967CE7ED-05E9-4031-9F3B-CFB826511554@alexanderonline.org> <87ljwfbdga.fsf@kassiopeya.MSHEIMNETZ> <752DA813-1B66-4FD1-B28E-3C23176BA13D@alexanderonline.org> <87r6679t1t.fsf@kassiopeya.MSHEIMNETZ> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kt422-0003Ec-2a for emacs-orgmode@gnu.org; Thu, 23 Oct 2008 13:31:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kt420-0003Dq-Dq for emacs-orgmode@gnu.org; Thu, 23 Oct 2008 13:31:33 -0400 Received: from [199.232.76.173] (port=34808 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kt420-0003DZ-5M for emacs-orgmode@gnu.org; Thu, 23 Oct 2008 13:31:32 -0400 Received: from mail.gmx.net ([213.165.64.20]:35943) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1Kt41z-0008QX-N7 for emacs-orgmode@gnu.org; Thu, 23 Oct 2008 13:31:32 -0400 In-Reply-To: (Avdi Grimm's message of "Thu, 23 Oct 2008 12:42:42 -0400") 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: emacs-orgmode Org-Mode "Avdi Grimm" writes: > A few points, from someone with a decent amount of testing background: Jippie! Please stay with us for a few days :-D > * As someone who has contributed to OS projects, the lack of a > pre-existing set of regression tests in org-mode is actually *the* > most significant blocker to my getting involved in org-mode > development. I do all of my coding - both professional and personal - > in the context of tests, and not having the existing framework means > that before I can start working on new features I first need to spend > time yak-shaving on testing infrastructure. > > * I think there's a lot of over-thinking going on here. Here's the > test-first coding discipline in a nutshell: > 1. Identify a problem/missing feature. > 2. Write a test (possibly using a unit-testing framework to help) > which will pass when the bug has been fixed or feature added. This can > be as simple as calling a function and validating its return value. > 3. Run the test. Verify it FAILS. > 4. Write code to make the test PASS. > 5. Refactor, if you introduced any code duplication in step 4. > 6. Run all the tests, to make sure you didn't break anything else. > 7. Commit. > > If someone would be so kind as to identify a small bug or feature, I > would be happy to demonstrate this workflow in the form of code, time > permitting. Sounds great! Not shure if we can provide a bug though :-D Bug anyone? Hm - how about: 1. A not yet existent elisp file test-worg.el, that defines a function hello-worg, and a variable lang, and simply puts "Hello Worg"into the minibuffer (if (string= lang "en")) and "Hallo Worg" (if (string= lang "de")) ? Did you work with unit-testing frameworks for elisp already? Which one? Recommendations? Could say something about the effort to get started with such a framework? Can we add it without changing Org's code? If understand 2. correctly - yes? If we can, would we loose quality/speed of tests? How much? Tell us all :-) Oha - I have an appointment (concert) - back tonight! All the best, -- Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover Tel.: +49 (0)511 - 36 58 472 Fax: +49 (0)1805 - 233633 - 11044 mobil: +49 (0)173 - 83 93 417 Email: s.rose@emma-stil.de, sebastian_rose@gmx.de Http: www.emma-stil.de