Hi Jian, Why we are using all static functions in 'BaseTelluriumJavaTestCase' ?
Some how I feel static will create lot of problems interms of JVM ? and Why can't our 'TelluriumTestNGTestCase' class itself set customConfig? Because I executed my selenium test cases [without tellurium] against selenium grid , but my test cases are not executing [it just halts] because I kept static as my SeleniumServer. Regards, Satyadev On Aug 5, 9:32 pm, John <[email protected]> wrote: > Hi, > > Tellurium does provide you the capability you want. You should use > BaseTelluriumJavaTestCase > instead of TelluriumJavaTestCase or TelluriumTestNGTestCase. > > If you look at the code of the two above classes, you will see what > they actually do are to setup and > tear down the tests. For instance, the TelluriumTestNGTestCase class > is defined as follows, > > public abstract class TelluriumTestNGTestCase extends > BaseTelluriumJavaTestCase { > > protected static TelluriumFramework tellurium; > > @BeforeClass > public static void setUpForClass() { > tellurium = TelluriumSupport.addSupport(); > tellurium.start(customConfig); > connector = (SeleniumConnector) tellurium.getConnector(); > } > > @AfterClass > public static void tearDownForClass() { > if(tellurium != null) > tellurium.stop(); > } > > } > > Since you want to have total control of the startup and tear down > procedures, > you can simply extend your test case from BaseTelluriumJavaTestCase > and then do whatever you want in a similar way as shown in the above > code. > > Thanks, > > Jian > > On Aug 5, 6:56 am, Evil Zub <[email protected]> wrote: > > > > > Hello again, > > > Thanks your quick answers! > > Let me clarify my question a little: What I really intended was to > > keep the browser window open after all tests are finished and > > Tellurium closes down. I find that convenient i.e. for developing and > > debugging tests, or for doing some setup prior to manual tests. > > > Regards, > > ez > > > On 5 Aug, 12:26, dominicm <[email protected]> wrote: > > > > I find if your jUnit fixture extends TelluriumJavaTestCase then it > > > will keep the browser session open across multiple tests. > > > > On Aug 5, 10:29 am, Haroon Rasheed <[email protected]> wrote: > > > > > As per my understanding, we currently do not have a mechanism to use one > > > > browser session accross multiple tests but we can add that. I have just > > > > created an issue for > > > > it.http://code.google.com/p/aost/issues/detail?id=238 > > > > > <http://code.google.com/p/aost/issues/detail?id=238>Cheers > > > > Haroon > > > > > 2009/8/5 Evil Zub <[email protected]> > > > > > > Hello, > > > > > > I am currently evaluating Tellurium and I think it is a quite nice > > > > > framework. However, I have one question: > > > > > Is there a way to keep tellurium from closing the browser once the > > > > > tests are finished (apart from putting a "pause()" at the end of a > > > > > testcase)? > > > > > > Regards, > > > > > ez- Hide quoted text - > > > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
