I've looked a little at it this afternoon, and there doesn't seem to be an easy ( *not totally intrusive*) Java way to do it, and my groovy is still very poor. I'll try to come back to this once I can add the code I need dynamically without mucking up thing too much..
Jas. On Jun 19, 8:54 am, Jian Fang <[email protected]> wrote: > Cool. Let us know how Tellurium works with loggingselenium later. > > Thanks, > > Jian > > On Fri, Jun 19, 2009 at 11:49 AM, Jason <[email protected]> wrote: > > > Sure thing. For now, I may take a stab at integrating with > > loggingselenium until 0.7.0 or something similar. > > > Thanks again, > > Jason > > > On Jun 19, 8:22 am, Jian Fang <[email protected]> wrote: > > > In 0.7.0, the dispatcher layer will be responsible to track all the > > timings > > > for each call to the Selenium server. > > > The good thing is that the screenshot for an exception is also captured > > in > > > the dispatcher layer. Thus, we can > > > add the screenshot name to the result class. For the other case, it is > > more > > > complicated. We need to refactor the report > > > class from the data driven test so that it can be used for the whole > > > framework. This may take some time because our first > > > priority is to finish command bundle and UI module caching. Please be > > > patient. > > > > Thanks, > > > > Jian > > > > On Fri, Jun 19, 2009 at 11:10 AM, Jason <[email protected]> wrote: > > > > > I had meant either, really. I didn't realize it was easy to > > > > incorporate them into a test result. So I'll bite -- how do you > > > > advise doing that? > > > > > Thanks -- I'm really, really enjoying working with Tellurium! > > > > > Jas. > > > > > On Jun 18, 10:26 pm, Jian Fang <[email protected]> wrote: > > > > > Jason, > > > > > > Good question. > > > > > > Right now, we first like to re-use some part of the reporting > > functions > > > > from > > > > > the data driven test > > > > > so that you can output the result in console or file in String or XML > > > > > format. XML is good > > > > > for you to post-process the result using other tools. > > > > > > The report format should include test name, expected value, actual > > value, > > > > > exceptions, timing, and so on. > > > > > > For "captured screenshots", do you mean the screenshot automatically > > > > > captured by Tellurium core or the one > > > > > programmatically captured by user? The screenshot file name is not > > > > difficult > > > > > to add to the test result. > > > > > > Thanks, > > > > > > Jian > > > > > > On Fri, Jun 19, 2009 at 12:53 AM, Jason <[email protected]> wrote: > > > > > > > Hi -- I'm curious about the test result reporting work to be done. > > > > > > One feature I'd love to see is something that integrates captured > > > > > > screenshots in with reports a la loggingselenium. What do you > > > > > > envision so far as far as reporting goes? > > > > > > > Thanks! > > > > > > Jason > > > > > > > On Jun 15, 7:28 am, John <[email protected]> wrote: > > > > > > > Hi all, > > > > > > > > Tellurium 0.6.0 will be out next week and we are planing for > > 0.7.0 > > > > > > > features. Our team plan to > > > > > > > add the following features: > > > > > > > > 1) Command bundle > > > > > > > 2) UI module caching > > > > > > > 3) Design and implement an advanced algorithm for group locating > > at > > > > > > > Engine side > > > > > > > 4) Widget architecture re-visit > > > > > > > 5) Built in support for trace information such as timing. > > > > > > > 6) More flexible name schema for UI templates, for example, you > > can > > > > > > > use "odd" and "even" for the name > > > > > > > 7) Add Exception code in Engine so that the Core can handle > > different > > > > > > > types of exceptions appropriately. > > > > > > > 8) Add table header alias so that you can use header alias to > > refer > > > > to > > > > > > > a column > > > > > > > 9) Add Widget archetype > > > > > > > 10) Add I18N support > > > > > > > 11) Add test utility packages such as testing cross site scripts, > > SQL > > > > > > > injections, mock objects, and more. > > > > > > > 12) Built in support for test result reporting > > > > > > > > In the meanwhile, we are open to users' suggestions. If you have > > any > > > > > > > new feature to propose, please follow up with this thread. > > > > > > > > Thanks, > > > > > > > > Tellurium team > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "tellurium-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/tellurium-users?hl=en -~----------~----~----~----~------~----~------~--~---
