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: Mon, 13 Aug 2012 12:11:33 -0400
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
From: "Joel C. Salomon" <[log in to unmask]>
Parts/Attachments: text/plain (23 lines)
On Mon, Aug 13, 2012 at 9:46 AM, Paulo Roberto Massa Cereda
<[log in to unmask]> wrote:
>>> One possibility is to have a test spec, so we can have a "generic"
>>> test infrastructure which reads this spec and "knows" how to perform
>>> a certain analysis.
>> Can you elaborate?  Currently we simply run some functions, and check
>> the output.
> I was just thinking out loud. :) I was thinking of a input format, say
> written in XML (/me looks at David) or another markup language, with a list
> of assertions, e.g, (sorry I don't know the innards of the tests neither L3
> sutff)
> <asserttrue input="\foo" expected="bar" />
> or something similar. To test a certain code snippet, a single test spec
> would suffice.

That looks to me like the technique of qstest’s `\Expect` macro.