[
https://issues.apache.org/jira/browse/JCR-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600776#action_12600776
]
angela commented on JCR-1629:
-----------------------------
> What features would this component test for that jcr-tests + jcr2spi don't
> already cover?
it would include tests running directly on the SPI interfaces. neither
jcr-tests nor the tests present with jcr2spi cover that, which means that any
implementor of the SPI interfaces can only indirectly test the implementation,
which can be quite cumbersome.
second we could move the generic SPI test-cases that are currently present in
the spi-commons project and provide them for other implementations.
third we had a place to put SPI related tests that arise from questions posted
to the dev/user-list and from the various discussions mostly related to missing
javadoc.
as stated above: if there is another way to achieve that, i'm perfectly happy
with another approach as well.
but i think that starting to build tests for the SPI would be valuable.
> SPI: Testsuite for the SPI Interfaces
> -------------------------------------
>
> Key: JCR-1629
> URL: https://issues.apache.org/jira/browse/JCR-1629
> Project: Jackrabbit
> Issue Type: New Feature
> Components: jackrabbit-spi
> Reporter: angela
>
> now that people start writing SPI implementations we should provide a
> test-suite that runs on the SPI directly in order to provide the developers a
> way to assert basic compliance of their implementation without having the JCR
> api in between.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
