On 20/05/15 18:48, Claude Warren wrote:
parallel for now, but I expect we would move a fair number of tests to it
as a replacement.
I'm not so sure replacement is the right thing to do and I'd welcome
veryone's thoughts. It would introduce a signifcant dependency on
org.xenei:junit-contracts. With all due respect, having longterm
(years!) jena testing depend on that is not ideal.
Andy
On Wed, May 20, 2015 at 10:25 AM, Andy Seaborne <a...@apache.org> wrote:
On 19/05/15 20:25, Claude Warren wrote:
There is a set of contract tests (and test helpers) on the
"add-contract-tests" branch. That branch works and has minimal change
from
the current tests. Those changes are adding the junit-contract runner and
plugins.
It makes no change to the execution.
The problem that I am having is keeping it up to date with the current
change rate of the Jena packages. Granted the contract tests are only
implemented for the jena-core module, we have been keeing the entire suite
up to date.
Is there anyone that has any objection to moving the contract tests to the
main code branch?
Seems like a good idea - would this be in parallel to the existing tests,
or a partial replacement?
Andy
Claude
