Hi Liang, UI module is really used for runtime Java object to locator mapping. The reason we put the UI module as a class level static variable is that JUnit requires static variables in the @BeforeClass method in order to share the variables among different test methods. Of course, you can put the UI module to method level and use it as a local variable. I don't think there is any constraint in Tellurium for that.
Thanks, Jian On Sun, Sep 27, 2009 at 4:56 AM, Liang HE <[email protected]> wrote: > Hi, > > We have testing scenarios crossing number of pages (10+). When I look at > the example Tellurium projects, UI modules are usually defined in class > level setup. That leads to large number of static variable which is regarded > as bad practice in test class. Do anybody have best practice organizing UI > modules to minimize the number? Is there any concern that I move defineUI to > method level setup? > > Thanks, > Liang HE > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
