Mailing-List: contact log4cxx-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4CXX Dev" <log4cxx-dev@logging.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-Id: <6.0.3.0.0.20050106113559.022a6a60@mail.qos.ch>
Date: Thu, 06 Jan 2005 11:45:46 +0100
To: "Log4CXX Dev" <log4cxx-dev@logging.apache.org>
From: Ceki =?iso-8859-1?Q?G=FClc=FC?= <ceki@qos.ch>
Subject: Re: cvs commit: logging-log4cxx/tests/witness/ndc NDC.1
In-Reply-To: <20050105224259.59902.qmail@minotaur.apache.org>
References: <20050105224259.59902.qmail@minotaur.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable


Curt,

While you are importing unit tests over from log4j, you probably
became aware that the log4j tests based on the witness approach,
although very valuable, are fragile and somewhat hard to maintain. I
suspect that better and cheaper testing methodologies are out there.

What do you think?

At 11:42 PM 1/5/2005, you wrote:
>carnold     2005/01/05 14:42:59
>
>   Modified:    include/log4cxx ndc.h
>                src      loggingevent.cpp ndc.cpp ttcclayout.cpp
>                         xmllayout.cpp
>   Added:       tests/input/ndc NDC1.properties
>                tests/src ndctestcase.cpp
>                tests/witness/ndc NDC.1
>   Log:
>   LOGCXX-51: Moving over NDC unit tests from log4j
>
>   Revision  Changes    Path
>   1.12      +21 -2     logging-log4cxx/include/log4cxx/ndc.h

[cut]

--=20
Ceki G=FClc=FC

   The complete log4j manual: http://www.qos.ch/log4j/