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

Chris M. Hostetter updated SOLR-15807:
--------------------------------------
    Attachment: SOLR-15807-2.patch
        Status: Open  (was: Open)

Bah ... yes, of course i would have fat-fingered / copy-pasted some o printable 
character into the code ... this is what i get for not reading the diff 
directly.

Updated _clean_ patch. 

I think this is good to go?

> Add a "LogListener" helper 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-1.patch, SOLR-15807-2.patch, 
> SOLR-15807.patch, screenshot-1.png
>
>
> 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

Reply via email to