MIME-Version: 1.0
References: <CAFUtaNGNykpg-mguMyiBv5kaCHBV9CsTYkt2EOeVg9JfJ0kPZw@mail.gmail.com>
            <5022BFB4.1090800@latex-project.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Message-ID:  <CAFUtaNHy+gYuBCJ0OaXv7CCu6TR+Ht+kqah6ga7eFrnPnqdS=Q@mail.gmail.com>
Date:         Wed, 8 Aug 2012 16:30:03 -0400
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@listserv.uni-heidelberg.de>
Sender: Mailing list for the LaTeX3 project <LATEX-L@listserv.uni-heidelberg.de>
From: "Joel C. Salomon" <joelcsalomon@GMAIL.COM>
Subject: Re: Examples of l3doc & unit testing?
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <5022BFB4.1090800@latex-project.org>
Precedence: list
Status: R

On Wed, Aug 8, 2012 at 3:36 PM, Frank Mittelbach
<frank.mittelbach@latex-project.org> wrote:
> Am 08.08.2012 19:34, schrieb Joel C. Salomon:
>
>> Is there a simple example somewhere of the use of l3doc’s \TestFiles,
>> \UnitTested, & \TestMissing commands? What sort of unit-tests are
>> these meant to document?
>>
>> (Or are these just meant to be dumb pointers to arbitrary kinds of
>> unit testing?)
>
> they are meant to document how much testing has been written in the
> regression test suite. The idea being that each interface function gets
> tested on standard and boundary cases (in the ./testfiles directories).
>
> but nothing scientific about really. It always depended on how well people
> wrote and write tests. Now at some point we did some attempt to sort out
> where we have tests and where we are still missing them.
>
> There is some support in the make file for this "make checktest"
>
> but we didn't quite got this properly going (yet)

And on Wed, Aug 8, 2012 at 3:54 PM, Joseph Wright
<joseph.wright@morningstar2.co.uk> wrote:
> Frank has covered what the idea is here. To see the tests themselves,
> take a look at the GitHub site: the tests don't go to CTAN.

Thank you both. I'll have to see whether & how to adapt that model to
my own programming style.

And since there's nothing l3-specific going on, I can get tips on
writing effective unit tests elsewhere (read: on TeX.SX) without
distracting this list. ;-)

(There shouldn't be any funny interactions between l3doc and qstest, right?)

—Joel