On 17/03/12 11:15, Danny Ayers wrote:
Hi all,

tl;dr : How are the the SPARQL 1.1 tests run against Fuseki?

tl;dr : arq.qtest --earl manifest.ttl

I decided it was time to put some functional tests in front of the
SPARQL 1.1 middleware thing I've been building [1], running against
Fuseki.

That looks interesting [9] -

I worked out pretty much what I needed [2], essentially a HTTP
client firing off messages to my front end. The preconditions,
request, response and postconditions will be pulled out of RDF
descriptions. The messages may potentially be any media type, though
my main focus will be HTML.

Another recent project had yielded a starter vocab for DSP systems [3]
- processors with parameters in pipelines (think XProc) which seems a
nice fit for describing the test harness itself (it was aimed at DSP
but the terms are generic, I think I'll rename it "Proc").

Then I discovered the SPARQL 1.1 tests [4]. D'oh! (I knew of but had
forgotten about the earlier DAWG tests).

There's considerable overlap with what I'm after, I reckon I can
extend/integrate a lot of it. But what I can't seem to find is any
test harness for running the tests, to get a clue how best to do the
pipeline side.

I've found some tests inside Fuseki itself but they seem to be more
"internal" than what I'm after.

Fuseki internal tests aren't DAWG/SPARQL-WG tests. There aren't any proper protocol tests currently. There are lots of query tests which are run by ARQ.

ARQ runs the WG test suite - there's a command line tool to run tests and if you point it at the "manifest-all.ttl" then it runs all the tests. There are some entailment and federate query tests that don't pass out-of-the-box, and (dev system only - temporary) some property path tests may not work as the WG considers PP changes. ARQ in dev has some proposed changes and these are different from the unmodified test suite.

There is also a test manifest parser that reads the manifest format and

It's not written to be extensible but taking a copy and hacking what you need might help.

        Andy


So any pointers/suggestions appreciated.

Cheers,
Danny.

[1] http://tinyurl.com/seki-overview
[2] https://github.com/danja/seki/blob/dev/src/tests/notes.txt
[3] http://hyperdata.org/xmlns/dsp/
[4] http://www.w3.org/2009/sparql/docs/tests/


[9] http://en.wikipedia.org/wiki/List_of_Go_terms#Seki

Reply via email to