emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Sebastien Vauban
	<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: [BUG] ob-sql.el: probably an extra paren
Date: Wed, 20 Mar 2013 14:47:56 +0100	[thread overview]
Message-ID: <87fvzqnpfd.fsf@bzg.ath.cx> (raw)
In-Reply-To: <86vc8mtfcx.fsf@somewhere.org> (Sebastien Vauban's message of "Wed, 20 Mar 2013 13:39:26 +0100")



Hi Sébastien,

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:

> Nick Dokos wrote:
>> Can we please make it an invariable practice to run `make test' before
>> every push?
>
> Isn't it possible to put such in some sort of Git pre-commit hook (or pre-push
> hook), so that it gets automatically enforced?

If anyone knows how to setup an automated tests framework for Org,
feel free to go ahead, we will use it and monitor broken tests to
see what's wrong in the code or in the tests or in the environment
running the tests.

Testing is a nice habit to have, but let's not make it a coercive
pre-requisit before pushing patches.  

My whole thinking here is well captured by Rich Hickey:

  http://codequarterly.com/2011/rich-hickey/

  Fogus: You have been known to speak out against test-driven
  development. Do you mind elaborating on your position?

  Hickey: I never spoke out ‘against’ TDD. What I have said is, life
  is short and there are only a finite number of hours in a day. So,
  we have to make choices about how we spend our time. If we spend it
  writing tests, that is time we are not spending doing something
  else. Each of us needs to assess how best to spend our time in order
  to maximize our results, both in quantity and quality. If people
  think that spending fifty percent of their time writing tests
  maximizes their results—okay for them. I’m sure that’s not true for
  me—I’d rather spend that time thinking about my problem. I’m certain
  that, for me, this produces better solutions, with fewer defects,
  than any other use of my time. A bad design with a complete test
  suite is still a bad design.

Best,

-- 
 Bastien

  reply	other threads:[~2013-03-20 13:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20  2:54 [BUG] ob-sql.el: probably an extra paren Nick Dokos
2013-03-20  6:47 ` Bastien
2013-03-20 12:39 ` Sebastien Vauban
2013-03-20 13:47   ` Bastien [this message]
2013-03-21  8:28     ` Achim Gratz
2013-03-21 13:41       ` Bastien
2013-03-21 14:03         ` Nicolas Richard
2013-03-21 16:58         ` Yagnesh Raghava Yakkala
2013-03-21 17:31           ` Bastien
2013-03-21 18:40             ` tests with travis-ci (was: [BUG] ob-sql.el: probably an extra paren) Yagnesh Raghava Yakkala
2013-03-21 20:41               ` tests with travis-ci Bastien
2013-03-21 22:20                 ` Yagnesh Raghava Yakkala
2013-03-22  7:56                   ` Yann Hodique
2013-03-22 10:40                     ` Yagnesh Raghava Yakkala
2013-03-31 19:07                       ` Yann Hodique
2013-03-22  6:40                 ` Andreas Röhler
2013-03-22 12:55                   ` Nick Dokos
2013-03-22 13:07                     ` Andreas Röhler
2013-03-21 17:38         ` [BUG] ob-sql.el: probably an extra paren Achim Gratz
2013-03-21 17:59           ` Bastien
2013-03-22  7:01             ` Achim Gratz
2013-03-22  7:36               ` Bastien
2013-03-22  7:59                 ` Achim Gratz
2013-04-06  0:46                   ` Bastien
2013-03-22 10:44               ` Yagnesh Raghava Yakkala
2013-03-21  8:37     ` Sebastien Vauban

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fvzqnpfd.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).