[
https://issues.apache.org/jira/browse/SOLR-15807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17446243#comment-17446243
]
David Smiley commented on SOLR-15807:
-------------------------------------
Ok; makes sense. But maybe we should start with a Rule and then add support
for additional scopes for when that's desired? This way you can just declare
the thing and not have a try-with-resource scope indentation in each test. I
guess you're kind of getting to that in your middle paragraph but I'm saying it
should be delivered this way initially so that the common case is simple.
> Add a "LogInterceptor" helpe class that makes it easy to inspect & assert
> expected log messages
> -----------------------------------------------------------------------------------------------
>
> Key: SOLR-15807
> URL: https://issues.apache.org/jira/browse/SOLR-15807
> Project: Solr
> Issue Type: Sub-task
> Reporter: Chris M. Hostetter
> Assignee: Chris M. Hostetter
> Priority: Major
> Attachments: SOLR-15807.patch
>
>
> Following on some of the ideas started/outlined in the parent task...
> we should have an easy way for a block of test code to "intercept" and make
> assertions about log messages from specific loggers (at specific log levels,
> matching specific substrings/regexes) that happen as a result of some actions
> during the test code.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
