Re: test status

I checked the current test suite:

What do we do about tests that are changed?
Probably better to delete the old one, withdraw it's name, and create a 
fresh separate test.  The current reports are reporting against the old 
tests and it's going to be safer avoid confusion here.


The following tests need work:

=== Does not reflect latest design

Test 105 :: STRBEFORE()
Test 106 :: STRAFTER()

=== No dataset

Test: UUID[] pattern match
** Failure:  UUID() pattern match
   No dataset

Test: STRUUID[] pattern match
** Failure:  STRUUID() pattern match
   No dataset

== Spec unstable at this point

Test: syntax-BINDscope7.rq
** Failure:  syntax-BINDscope7.rq(com.hp.hpl.jena.sparql.junit.SyntaxTest)
   Expected parse failure

Test: syntax-BINDscope8.rq
** Failure:  syntax-BINDscope8.rq(com.hp.hpl.jena.sparql.junit.SyntaxTest)
   Expected parse failure


== BINDINGS has gone:

Test: BINDINGS with subj-var, 1 row
** Failure:  BINDINGS with subj-var, 1 row

Test: BINDINGS with obj-var, 1 row
** Failure:  BINDINGS with obj-var, 1 row

Test: BINDINGS with 2 obj-vars, 1 row
** Failure:  BINDINGS with 2 obj-vars, 1 row

Test: BINDINGS with 2 obj-vars, 1 row with UNDEF
** Failure:  BINDINGS with 2 obj-vars, 1 row with UNDEF

Test: BINDINGS with 2 obj-vars, 2 rows with UNDEF
** Failure:  BINDINGS with 2 obj-vars, 2 rows with UNDEF

Test: BINDINGS with pred-var, 1 row
** Failure:  BINDINGS with pred-var, 1 row

Test: BINDINGS with [OPTIONAL] obj-var, 1 row
** Failure:  BINDINGS with (OPTIONAL) obj-var, 1 row

Test: BINDINGS with subj/obj-vars, 2 rows with UNDEF
** Failure:  BINDINGS with subj/obj-vars, 2 rows with UNDEF

Test: syntax-bindings-02.rq
** Error:    syntax-bindings-02.rq(com.hp.hpl.jena.sparql.junit.SyntaxTest)

Test: syntax-bindings-03.rq
** Error:    syntax-bindings-03.rq(com.hp.hpl.jena.sparql.junit.SyntaxTest)

Test: syntax-bindings-04.rq
** Error:    syntax-bindings-04.rq(com.hp.hpl.jena.sparql.junit.SyntaxTest)

Test: syntax-bindings-05.rq
** Error:    syntax-bindings-05.rq(com.hp.hpl.jena.sparql.junit.SyntaxTest)

Received on Tuesday, 29 May 2012 13:44:21 UTC