MIME-Version: 1.0
References: <LATEX-L%201208101400309140.36EB@LISTSERV.UNI-HEIDELBERG.DE>
            <502502DA.7050009@gmail.com>
            <CANQYN6y9eA9YqVg+MoYoG4fWp4VPAY3rFhRJNz1WQKvwhh3thQ@mail.gmail.com>
            <5029052A.2090507@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Message-ID:  <CAFUtaNFF3Bf6FAYUE4wE-79fiwreWVutnFKVtqUHtP8iBsO00Q@mail.gmail.com>
Date:         Mon, 13 Aug 2012 12:11:33 -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:  <5029052A.2090507@gmail.com>
Precedence: list
Status: R

On Mon, Aug 13, 2012 at 9:46 AM, Paulo Roberto Massa Cereda
<cereda.paulo@gmail.com> 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.

--Joel