User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713
            Thunderbird/14.0
MIME-Version: 1.0
References: <CAFUtaNGNykpg-mguMyiBv5kaCHBV9CsTYkt2EOeVg9JfJ0kPZw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Message-ID:  <5022BFB4.1090800@latex-project.org>
Date:         Wed, 8 Aug 2012 21:36:20 +0200
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: Frank Mittelbach <frank.mittelbach@LATEX-PROJECT.ORG>
Subject: Re: Examples of l3doc & unit testing?
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <CAFUtaNGNykpg-mguMyiBv5kaCHBV9CsTYkt2EOeVg9JfJ0kPZw@mail.gmail.com>
Precedence: list
Status: R

Am 08.08.2012 19:34, schrieb Joel C. Salomon:
> Folks,
>
> 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)

frank