- From: Jeen Broekstra <jeen.broekstra@aduna.biz>
- Date: Wed, 29 Mar 2006 11:27:04 +0200
- To: RDF Data Access Working Group <public-rdf-dawg@w3.org>
The current test suite contains test cases for both query evaluation and for query syntax testing. These are essentially different ball games. To reflect this, Andy has already come up with a different manifest format for syntax test cases but many tests still use the 'query' manifest format (leaving out the result property). Essentially, a syntax test entry as proposed by Andy has three properties: [] rdf:type mf:TestSyntax ; # to indicate it is a syntax test mf:name "..." ; # test name, as usual mf:action <query-file.rq> # file with query to be syntax-tested The 'old' format used for syntax tests is: [] mf:name "..."; mf:action [ qt:query <query-file.rq> ; qt:data <empty.nt> ] ; I happen to agree with Andy that his format is more clear and more compact. Is everyone ok with me explicitly creating separate suites for syntax and query evaluation tests and using Andy's proposed manifest format for the syntax tests? I'm happy to do a quick rewrite of the relevant manifest (/tests/data/SyntaxFull/manifest.ttl). Btw, I'm planning to create these separate suites by creating one or two 'meta-manifests' that indicate which sets of tests to use for which purposes (one for all query-test manifests that are relevant to implementations of the latest WD, and perhaps one for all syntax tests). This will enable implementors to have a single entry point that tells them exactly which tests they should use for their implementation (and which they should ignore...). Jeen -- Jeen Broekstra Aduna BV Knowledge Engineer Julianaplein 14b, 3817 CS Amersfoort http://aduna.biz The Netherlands tel. +31 33 46599877
Received on Wednesday, 29 March 2006 09:27:44 UTC