One must take care to not mix two concepts: reporting and monitoring.
Reporting uses sysout or files and reports the outcomes of the stories
down to step level.
Monitoring is more technical and typically has a silent no-op impl. It
typically is used for debugging.
Looks like you may be looking to have a logging impl of monitoring.
That could be achieved easily.
On 12/05/2014 20:54, Alex Filatau wrote:
>> "What use case are you trying to satisfy? Having say debug-level
logging being always written to a file in the background?"
That's actually a good question. I was considering to implement
something for me project that will allow main output (steps executed
etc) to still use System.out, but some information (mostly debug and
performance related, like request/response chatter in API tests) to be
logged in background to some file so that in case of a need I could
always open that separate log and get info I was dumbing there for
debug purposes.
I was planning to use independent logger implementation slf4j not
using JBehave classes for this, but not wandering if it makes sense to
provide own implementation for StepMonitor indeed. From your
experience, what would be some pro and contra here?
Regards,
Alex.
On Mon, May 12, 2014 at 11:41 AM, Mauro Talevi
<mauro.tal...@aquilonia.org <mailto:mauro.tal...@aquilonia.org>> wrote:
All components - including monitors - are configurable so you can
swap the default with your own:
http://jbehave.org/reference/stable/configuration.html
What use case are you trying to satisfy? Having say debug-level
logging being always written to a file in the background?
On 12 May 2014, at 19:21, Frank Pedroza <fpedr...@part.net
<mailto:fpedr...@part.net>> wrote:
Could you help me understand this a bit more or point me to
something that explains how I would configure the jbehave
framework to support this?
On Fri, May 9, 2014 at 4:12 PM, Mauro Talevi
<mauro.tal...@aquilonia.org <mailto:mauro.tal...@aquilonia.org>>
wrote:
JBehave uses the monitor pattern that allows you to honour
dependency injection properly. Most logging frameworks rely
on static lookup mechanisms.
If you want to use a logging framework you can still do so by
providing a logging implementation of the relevant interfaces.
Cheers
> On 9 May 2014, at 22:09, Frank Pedroza <fpedr...@part.net
<mailto:fpedr...@part.net>> wrote:
>
> I'm new to the group so sorry if this isn't the right venue
for this sort of question or if this has already been
addressed, but why is any of the JBehave framework using
System.out rather than something like slf4j?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
--------------------------------------------
Frank M. Pedroza - Software Engineer
Partnet - Development
801.708.5050 <tel:801.708.5050>
-----------------------------------------------------------------
The nice part about being a pessimist is that you are constantly
being either proven right or pleasantly surprised.
-- George F. Will
