On 25/04/15 13:17, Claude Warren wrote:
Bruno,
When I was working on the tests I moved many of the methods that were in
the base test classes into classes in the testing_framework package. The
packackage is visible at
http://svn.apache.org/viewvc/jena/Experimental/new-test/src/test/java/com/hp/hpl/jena/testing_framework/?pathrev=1525332
I would like to move these into the new tests that we are building as they
help with the contract tests and provide standard implementations for
various functions that make testing easier (e.g. creating a triple from the
string "<a> <b> <c>")
SSE.parse* has that machinery (in the wrong module ATM :-()
If teh testing code all goes through one static it can use the old NT or
TTL (prefixes) reader for now depending on how clever you want that to be.
Think that the package should be in the jena-core test source tree.
Does anyone see any reason not to do this?
Would that be as a separate hierarchy for now? i.e. two test suites? It
just means that working on new tests isn't a blocker so you can finalize
it as and hen you have the time.
Also, I think that the contract tests should be created in the jena3 branch
until that is moved to to the master.
That move is going to happen very soon unless there is a reason not to.
It is ready to go. Much can still be done but it builds and is
usable. When in master, we can start SNAPSHOT builds.
If anyone wants to check it against their application code, it's good
for that.
Andy
Claude
