May be discussion is better on dev@ while the wiki is good for creating
and collecting long term material but poor for discussion.
I'm interested as time permits.
It would be good to have these tests - example: I'd like to consider a
change (jena3) to the implementation of graph events to have the basic
graph not event-aware and add a wrapper to do the event triggers. It
would make extensions cleaner. The most basic graph interface is little
more than add/delete/find. Contract tests would pin down external
functionality.
Andy
On 06/08/14 18:46, Claude Warren wrote:
I think I have some time again to look at testing some more. The last time
I dove into it I learned quite a bit, but I don't think I improved on the
existing testing at all.
However, with time to reflect and movement forward of the system I think
that perhaps we should think about defining the SPI and what the contracts
are for the SPI.
I would like to take a crack at the following:
1) getting consensus on what classes/interfaces are part of the basic SPI
(e.g. Graph interface / GraphBase class)
2) document the contracts for those classes. (e.g. adding a triple to graph
triggers notification of listeners)
3) write contract tests for those classes/interfaces. (
https://github.com/Claudenw/junit-contracts) This should result in a set
of tests that are simple to extend/implement and will ensure that
implementations implement the entire contract correctly.
With this in mind, what is the best forum for this discussion? Who is
interested in participating in the discussions? Who is interested in
helping to build the contract tests?
I was thinking about the wiki as a place to hold the discussions.
Thoughts?
Claude
