[JENA-1922] Remove use of JUnit3 for manifest driven tests.

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Jena 3.15.0
• Fix Version/s: Jena 3.16.0
• Component/s: ARQ, TDB, TDB2
• Assignee: Andy Seaborne
• Reporter: Andy Seaborne
• Created: 22/Jun/20 10:30
• Updated: 13/Jul/20 15:51
• Resolved: 24/Jun/20 12:16

Description

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.