Skip to content

Upgrade JUnit usage in jena-core testing #3236

Open
@afs

Description

@afs

jena-core testing is mixture of JUnit3 and JUnit4.
This risks missing tests from surefire. (Some JUnit4-only tests were being missed because discovery wasn't finding them.)

There does not appear to be any blockers for moving updating everything to JUnit4 (transition), then to JUnit5 now contract testing is no longer used.

JUnit4 to JUnit5 is a simpler task.

Going via JUnit4 reduces the chances of missing things.

The test would still be organised into test suites, not relying on discovery to check that everything is being run.

Elsewhere, Jena has some custom JUnit4 test runners that build tests from manifestsfor RDF, SPARQL, SHACL and ShEx.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions