jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davide Giannella (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-4177) Tests on Mongo should fail if mongo is not available
Date Tue, 04 Jun 2019 15:35:10 GMT

     [ https://issues.apache.org/jira/browse/OAK-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Davide Giannella updated OAK-4177:
    Fix Version/s: 1.16.0

> Tests on Mongo should fail if mongo is not available
> ----------------------------------------------------
>                 Key: OAK-4177
>                 URL: https://issues.apache.org/jira/browse/OAK-4177
>             Project: Jackrabbit Oak
>          Issue Type: Test
>            Reporter: Davide Giannella
>            Assignee: Davide Giannella
>            Priority: Major
>             Fix For: 1.14.0, 1.16.0
> Most if not all of the IT/UT that run against mongodb have an
> assumption at class level that if mongodb is not available the tests
> are skipped.
> The tests should fail instead if mongodb is not available and we
> explicitly said that, via the {{nsfixtures}} flags, we want to run the
> tests against mongodb.
> We currently have 4 fixtures/flags: DOCUMENT_NS, SEGMENT_MK,
> https://github.com/apache/jackrabbit-oak/blob/f957b6787eb7a70eba454ceb1cae90bd4d47f15c/oak-commons/src/test/java/org/apache/jackrabbit/oak/commons/FixturesHelper.java#L46
> We may have the need to introduce a new Fixture/Flag that indicate
> that we want to run the tests against Document using the in-memory
> implementation. For example: DOCUMENT_NS_IM.
> This will be useful on the Apache Jenkins as we don't have mongo there
> but we still want to run all the possible Document NS tests against
> the in-memory implementation when this is possible.
> /cc [~mreutegg]

This message was sent by Atlassian JIRA

View raw message