LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Wed, 8 Aug 2012 21:36:20 +0200
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
Message-ID: <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=UTF-8; format=flowed
From: Frank Mittelbach <[log in to unmask]>
Parts/Attachments: text/plain (24 lines)
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)