On Jan 19, 2007, at 8:55 AM, Tim Mattox wrote:
>> Are you talking about some other output? Or are you asking for
>> something in (parentheses)?
> Sorry, I wasn't clear. The current output for each test in the
> debug file
> usually includes a line "test_result: X" with X replaced by a number.
> However, for tests that fail outright, this line is missing. This
> line happened to correspond to the tests that had a newline in the
> message that I discussed (snipped) above.
> Please don't put in the parentheses things. That was just me
> on which number meant what.
>> 2. there would be no need for screen scraping/parsing; you would have
>> the data immediately available and all you have to do is output it
>> into the format that you want. We should be able to accommodate
>> whatever you need via an MTT Reporter plugin. I'm guessing this
>> should be pretty straightforward...?
> Where can I find some documentation for or examples of a plugin?
Probably my phone number. :-\
All the current Reporter plugins are in lib/MTT/Reporter/*.pm.
MTTDatabase.pm is the most comprehensive, but the others are quite
functional (Email.pm, TextFile.pm, INIFile.pm). The interface should
be rather straightforward:
Init: Called when the MTT client initializes.
Finalize: Called when the MTT client finalizes.
Submit: Called when the MTT client wants to submit something. If you
look at the output from a Verbose run of the MTT client, you can see
that this function is invoked at the end of each test run phase
I'm sure you'll have my questions -- feel free to ping me/Ethan with
whatever you need.
Server Virtualization Business Unit