You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Andrei Dulceanu (Jira)" <ji...@apache.org> on 2024/01/25 08:41:00 UTC

[jira] [Created] (OAK-10629) Refactor test functionality to check for log messages in oak-segment-*

Andrei Dulceanu created OAK-10629:
-------------------------------------

             Summary: Refactor test functionality to check for log messages in oak-segment-*
                 Key: OAK-10629
                 URL: https://issues.apache.org/jira/browse/OAK-10629
             Project: Jackrabbit Oak
          Issue Type: Task
          Components: segment-azure, segment-tar
            Reporter: Andrei Dulceanu
            Assignee: Andrei Dulceanu


Currently we're using this in [DefaultSegmentWriterTest|https://github.com/apache/jackrabbit-oak/blob/6a04b335eeaf9b7cb7f689605463c3ac0c38b269/oak-segment-tar/src/test/java/org/apache/jackrabbit/oak/segment/DefaultSegmentWriterTest.java#L319], but in OAK-10615 the same code was copy-pasted in [ToolUtilsTest|https://github.com/apache/jackrabbit-oak/blob/8cab6c5b3ae232baf3920c9039afa950dbf65b55/oak-segment-azure/src/test/java/org/apache/jackrabbit/oak/segment/azure/tool/ToolUtilsTest.java#L168-L182].

It would be nice to abstract this in its own utility class to avoid code duplication. Other usages in Oak [0].

[0] https://github.com/search?q=repo%3Aapache%2Fjackrabbit-oak%20ILoggingEvent&type=code



--
This message was sent by Atlassian Jira
(v8.20.10#820010)