tag:blogger.com,1999:blog-4110180.post6084730132221502095..comments2023-06-20T05:31:24.545-07:00Comments on Tapestry Central: TestNG and SeleniumAnonymoushttp://www.blogger.com/profile/04486596490758986709noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-4110180.post-48716611987788166292009-12-06T17:31:22.766-08:002009-12-06T17:31:22.766-08:00I wanted to tackle similar issues myself recently ...I wanted to tackle similar issues myself recently (esp. relating to jetty and selenium versions) and i went for the IMHO fastest+smallest solution: use maven-jetty-plugin and selenium-maven-plugin and just have them start at the pre-integration-test phase... I even got rid of some code!<br />Anyway, i'm also waiting to see how WebDriver/Selenium2 evolves - would love to have my tests also run on pure jvmAndreas Andreouhttps://www.blogger.com/profile/00388752405451056658noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-33684068578678190452009-12-04T03:58:46.245-08:002009-12-04T03:58:46.245-08:00Great news.
I have done similar changes to Abstrac...Great news.<br />I have done similar changes to AbstractIntegrationTestSuite to avoid starting a new Firefox for each test. Actually, without this it would be unusable for more that a couple of tests.<br /><br />I wonder if tapestry-test could be completely separate project from the tapestry itself ? Currently those two are quite independent. I have run tapestry-test 5 against tapestry 4 application, and actually can run it against whatever Java web application.altumanohttps://www.blogger.com/profile/07644069616370903161noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-68161468051820874852009-12-03T19:56:44.942-08:002009-12-03T19:56:44.942-08:00Have you thought about abstracting over WebDriver ...Have you thought about abstracting over WebDriver instead of Selenium? It might make some things easier, and would allow you to switch back and forth between native browser and pure JVM (via HtmlUnit) testing if you wanted to...Gredlerhttps://www.blogger.com/profile/09665588722297336518noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-89185567734604092352009-12-03T11:51:42.639-08:002009-12-03T11:51:42.639-08:00Thanks for the detailed information on your soluti...Thanks for the detailed information on your solution with selenium. It looks realy good.<br /><br />We had the same problem, running a project with jetty6 and doing testing with testng and selenium, but used another approach. <br />As you mentioned there is a Problem that there are conflicts between jetty6 and the packaged jetty5 that comes with selenium. My initial approach was a patch of the selenium server and the accompanied jetty 5 so that there were no conflict anymore. Since this approach was quite cumbersome for each update of selenium. We packaged the whole selenium server within a jar. (so a jar file within a jar) and started the selenium server through a separate classloader in the @BeforeSuite section. So we could start the webapplication under test together with an embedded jetty6 without any conflicts.<br />So creating integration tests is not more as subclassing this base class and writing TestNG with selenium remote control.<br />Perhaps this approach could also be helpful for you. <br /><br />-Robertspeedskaterhttps://www.blogger.com/profile/13707546251240846323noreply@blogger.com