[
https://issues.apache.org/jira/browse/JENA-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143790#comment-17143790
]
ASF subversion and git services commented on JENA-1922:
-------------------------------------------------------
Commit b32352562c08990d6ebb3846b4100e6d8a835c3a in jena's branch
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=b323525 ]
JENA-1922: Runners for test sets using W3C test manifests
> Remove use of JUnit3 for manifest driven tests.
> -----------------------------------------------
>
> Key: JENA-1922
> URL: https://issues.apache.org/jira/browse/JENA-1922
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ, TDB, TDB2
> Affects Versions: Jena 3.15.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
> Fix For: Jena 3.16.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Tests driven by manifest files use JUnit3 TestSuite features to build the
> test tree. There isn't an equivalent facility in JUnit4 but JUnit4 includes a
> copy of JUnit3.
> Construction of tests using JUnit3 TestSuite is used in:
> * jena-core: for legacy Turtle parser (minor, used for jena-core tests)
> * jena-arq - SPARQL and RIOT tests
> * jena-tdb, jena-tdb2.
> * jena-sdb
> * jena-iri
> This ticket is to replace the JUnit3 features with JUnit4 runners in
> jena-arq, jena-tdb and jena-tdb2 (the majority of the usage, counting test
> numbers)
> jena-core will be left alone (the legacy Turtle parser exists to parse
> jena-core test data e.g.assemblers).
> jena-iri will be left alone.
> jena-sdb is complex because tests also use a list of store configurations so
> do not naturally fit into the Runners needed for manifests. Code will be
> copied into jena-sdb to keep the existing scripted tests working using JUnit3
> style.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
