Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1E806EBB0 for ; Thu, 28 Feb 2013 13:05:28 +0000 (UTC) Received: (qmail 52201 invoked by uid 500); 28 Feb 2013 13:05:20 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 50405 invoked by uid 500); 28 Feb 2013 13:05:18 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 49531 invoked by uid 99); 28 Feb 2013 13:05:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2013 13:05:18 +0000 Date: Thu, 28 Feb 2013 13:05:17 +0000 (UTC) From: =?utf-8?Q?Jan_H=C3=B8ydahl_=28JIRA=29?= To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (SOLR-543) AbstractSolrTestCase should have automatic check for loggd exceptions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SOLR-543?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] Jan H=C3=B8ydahl updated SOLR-543: ----------------------------- This issue has been inactive for more than 4 years. Please close if it's no= longer relevant/needed, or bring it up to date if you intend to work on it= . SPRING_CLEANING_2013 =20 > AbstractSolrTestCase should have automatic check for loggd exceptions > --------------------------------------------------------------------- > > Key: SOLR-543 > URL: https://issues.apache.org/jira/browse/SOLR-543 > Project: Solr > Issue Type: Test > Reporter: Hoss Man > > SOLR-509 and SOLR-541 got me thinking: it would be really nice if Abstrac= tSolrTestCase had some code such that: > * setUp() registered a LogHandler that kept a record of any LogRecord tha= t was: > ** SEVERE > ** WARNING > ** contained a Throwable > * assertLog(Level, Class) could be called in the body of test = methods to ensure that at a certain point a LogRecord with a particular lev= el and/or type of Throwable had in fact been logged and note that it was ex= pected. > * tearDown() would inspect the LogHandler to assert no LogRecords exist t= hat have not already been noted as expected. > Something like this would allow us to make sure that nothing "bad" was ge= tting logged even if the API being tested presented a happy shiny face to t= he world -- and to check that in situations where something bad *should* be= logged, that it is. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org