[
https://issues.apache.org/jira/browse/OAK-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253697#comment-15253697
]
Davide Giannella commented on OAK-4259:
---------------------------------------
Let's reuse the {{nsfixtures}} we already have and the
[FixturesHelper|https://github.com/apache/jackrabbit-oak/blob/trunk/oak-commons/src/test/java/org/apache/jackrabbit/oak/commons/FixturesHelper.java].
If it would actually be possible, I would look into the possibility to
make {{FixturesHelper}} a sort-of factory that can be used to retrieve
the actual Fixtures to create the repository. For example the
{{NodeStoreFixture}}.
Didn't investigate about dependencies, circular-depencendies and
similar.
> Implement fixtures for running again oak-segment and/or oak-segment-next
> ------------------------------------------------------------------------
>
> Key: OAK-4259
> URL: https://issues.apache.org/jira/browse/OAK-4259
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: segment-next
> Reporter: Michael Dürig
> Labels: testing
>
> We need fixtures to run UTs / ITs against either or both segment
> implementations {{oak-segment}} and {{oak-segment-next}}.
> Ideally we can enable them individually through e.g. environment variables. A
> standard build would run against {{oak-segment}} so not to affect others.
> {{oak-segment-next}} could be enabled on request locally or for the CI.
> Once we deprecate {{oak-segment}} we would switch the default fixture to
> {{oak-segment-next}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
