Re: Parser validation/test suites ?

Hans-Peter Diettrich <DrDiettrich1@aol.com>
10 Aug 2006 15:46:24 -0400

          From comp.compilers
Related articles
Parser validation/test suites ? kennheinrich@sympatico.ca (Kenn Heinrich) (2006-08-09)
Re: Parser validation/test suites ? 148f3wg02@sneakemail.com (Karsten Nyblad) (2006-08-10)
Re: Parser validation/test suites ? DrDiettrich1@aol.com (Hans-Peter Diettrich) (2006-08-10)
Re: Parser validation/test suites ? Colin_Paul_Gloster@ACM.org (Colin Paul Gloster) (2006-08-14)
Re: Parser validation/test suites ? diablovision@yahoo.com (2006-08-14)
| List of all articles for this month |
From: Hans-Peter Diettrich <DrDiettrich1@aol.com>
Newsgroups: comp.compilers
Date: 10 Aug 2006 15:46:24 -0400
Organization: Compilers Central
References: 06-08-043
Keywords: testing
Posted-Date: 10 Aug 2006 15:46:23 EDT

Kenn Heinrich wrote:


> And how would you best indicate pass or fail? I've seen systems using
> special embedded comments that should match a compiler output, parsed
> out and chcked by a test suite dispatcher script, as well as systems
> that organize "good" source in one directory, "should fail with error
> XXX" sources in directory "XXX". What are some of the other schemes
> the masters recommend?


Test suites, for e.g. libraries, include files with the expected program
output. A compiler IMO can be tested just the same way, using the error
log for the output-to-match.


DoDi


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.