From: Michal Sojka <sojkam1@fel.cvut.cz>
To: notmuch@notmuchmail.org
Date: Sat, 6 Feb 2010 11:40:18 +0100
User-Agent: KMail/1.12.4 (Linux/2.6.31-1-686; KDE/4.3.4; i686; ; )
References: <123554aa0911200056h73def158pb0db64a2a78ed687@mail.gmail.com>
	<87vdgxqepm.fsf@yoom.home.cworth.org>
	<87d40jpkzj.fsf@yoom.home.cworth.org>
In-Reply-To: <87d40jpkzj.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="windows-1250"
Content-Transfer-Encoding: 7bit
Message-Id: <201002061140.18833.sojkam1@fel.cvut.cz>
Subject: Re: [notmuch] notmuch new: Memory problem (with uuencoded content)
Precedence: list

On Friday 05 of February 2010 19:59:12 Carl Worth wrote:
> Of course, I also pushed a set of tests to the test suite for this, (and
> some new "notmuch search" tests while I was at it).

Hi Carl,

I've just looked at your notmuch-test commits. Did you noticed my patches 
which port Git's test framework for use with notmuch? That framework has the 
same spirit as yours (shell scripting, easy to use) but compared to your 
current test script it has some nice features:

- Test suite is split into several files. Therefore you do not need to run the 
whole test suit when you are working in one area of notmuch.
- If some test fails, the executed commands are automatically displayed from 
which you can immediately see what was the problem.
- Working directory for each test has a fixed name based on the name of the 
script (no $$) so you know where to look if some test fails.
- You can decide whether you want to stop on the first failure or complete the 
whole test suite.
- At the end the results are summarized so you do not need to watch the output 
of the test suite.

It is straightforward to convert your current test script to Git's framework. 
If you are interested I'll do it.

Michal