Hi.
Remove the logger and have it in examples instead.
Jarmo.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Watir General" group.
To post to this group, send email to watir-general@googlegroups.com
Before posting
Hi,
On 14/11/2008, Chuck vdL <[EMAIL PROTECTED]> wrote:
>
> OTOH I really would like to see some kind of fully integrated
> 'logging' built into watir.. Somethig where I could just set a flag
> to enable the logging and specify a few things like where to establish
> the logging file, and the
I think JArkelen points out something fairly valuable here.
we're overloading the term 'logger' and that's causing confusion..
perhaps using more distinct nomenclature would be good?
In my view there is both "Logging" used for debugging of scripts or
how exactly the application is failing when s
Sorry for any confusion.
Yes, my question is whether people would like to have logging of Watir
driver actions embedded in Watir.
Cheers,
Alister
On Nov 14, 2:40 am, Bret Pettichord <[EMAIL PROTECTED]> wrote:
> I agree that it would be great if we had a way to log all of the watir
> driver acti
I use to kinds of logs in my test:
1. In all my self created classes and methods I use puts statements to
output the test case flow to the command window. This is for myself to
investigate quckly when something goes wrong.
2. I have a self created report class which creates nice html reports
with
I have not needed logger for watir internal methods.
However I do use logger for my tests using Logger class in Ruby for some
test noise generation
Here is a hacked up example which is sufficient for my needs.
here is a gist: http://gist.github.com/3466
my two.to_a cents
--
marekj | i can has wa
I agree that it would be great if we had a way to log all of the watir
driver actions. I've thought about doing this for years but have never
really had the need for it, and it is non-trivial to implement (although
the refactoring i've done shouldn't make this any harder to do).
If Alister's q
when I put the original logger in to watir, I really only intended it to get
overwritten by a plugged in logger, but this unfortunately caused a lot of
confusion. Probably cos the way I implemented it wasnt the best.
A common thing is for people to want to log that they are clicking a certain
link
I think you've misunderstood some comments that I made.
Someone pointed out that the WatirLogger was in Watir but not in
FireWatir. In response, I suggest that instead of putting it in both, we
remove it. Here is the code in question:
class WatirLogger < Logger
def initialize(filName, lo
