Comments on: Maven Selenium

By: soumya

soumya — Thu, 01 Sep 2011 08:52:53 +0000

Dear friends

I am trying to convert html test to java but could not find Java(JUnit)-Selenium RC in my selenium ide

could you please help me..

thank you in advance

By: John

John — Fri, 26 Aug 2011 08:49:09 +0000

Hello Vineet,

to completely automate tests, one ideally would like to automate also the packaging of the webapp
into .war, its deployment on a webserver, and starting the web server so that maven waits until
it starts and then starts to run the selenium tests. Do you have some idea on how to do this? I can
only think of some heavy weight solution – Maven calls a custom plugin which starts an external
process, which packages the .war, deploys it into the deployment directory of a webserver on the
file system, then calls run.bat or whatever of the webserver to get it started, and then waits
for some fixed amount of time before it tries to run selenium tests. Can you think of a more elegant
approach?

By: Meena

Meena — Wed, 24 Aug 2011 12:49:06 +0000

Hi Vineet, i am using selenium grid, c#, mbunit and Gallio to run my test case parallel but only 1 test case is running successfully other test cases are showing different error message like “Selenium.SeleniumException: ERROR: Got a null result
at Selenium.HttpCommandProcessor.DoCommand(String command, String[] args) in c:\hudson\workspace\selenium-rc-trunk-win-headless\trunk\clients\dotnet\src\Core\HttpCommandProcessor.cs:line 98
at Selenium.DefaultSelenium.Click(String locator) in c:\hudson\workspace\selenium-rc-trunk-win-headless\trunk\clients\dotnet\src\Core\DefaultSelenium.cs:line 166
at GDA.MyClass.TheUntitledTest12() in c:\Users\mnarvariya\Desktop\Junit\GDA\GDA\MyClass.cs:line 63″

Please Reply ASAP
Thanks,
Meena

By: Sergio Carabetta

Sergio Carabetta — Wed, 29 Jun 2011 13:23:06 +0000

@Anging,

I think your problem is the browserType field, it should be like:

selenium = new DefaultSelenium(“localhost”, 4444, “*firefox”, “http://10.151.124.159:7101/”);

By: anjing

anjing — Wed, 27 Apr 2011 10:10:06 +0000

selenium = new DefaultSelenium(“localhost”, 4444, “C:\\Program Files\\Mozilla Firefox\\firefox.exe”, “http://10.151.124.159:7101/”);
selenium.start();

I can’t run my test case if I setUp firebox browser,but iexplore is OK.

selenium = new DefaultSelenium(“localhost”, 4444, “*iexplore”, “http://10.151.124.159:7101/”);
selenium.start();

By: John Anderson

John Anderson — Sun, 27 Mar 2011 20:27:45 +0000

Vineet,

Great article for Maven Selenium setup. I just follwed your steps but I never can successfully test my selenium test cases, although I can see both jetty server startup and selenium startup on the console. When I commented out the section (pom.xml) of start selenium-server and manually started selenium server, then I ran mvn integration-test and it worked fine. If I commented out the executions section of starting jetty server and manually started jetty server by executing mvn cargo:start, integration-test also worked fine. If I leave both start jetty server and selenium-server in place, and when I tested selenium test cases, I always got HTTP ERROR: 404.

By: Kamal

Kamal — Thu, 03 Feb 2011 15:30:56 +0000

I am new to selenium and have just created a new test which I am trying to run on hudson.

I keep getting timed out waiting for profile to be created error

runSeleniumTests:

BUILD SUCCESSFUL
Total time: 0 seconds
java -jar /home/locgrdd/.hudson/jobs/SeleniumTest/workspace/selenium-server.jar -htmlSuite *firefox http://www.bbc.co.uk/weather /home/locgrdd/.hudson/jobs/SeleniumTest/workspace/TestSuite1.html /home/locgrdd/.hudson/jobs/SeleniumTest/workspace/results.html
[workspace] $ java -jar /home/locgrdd/.hudson/jobs/SeleniumTest/workspace/selenium-server.jar -htmlSuite *firefox http://www.bbc.co.uk/weather /home/locgrdd/.hudson/jobs/SeleniumTest/workspace/TestSuite1.html /home/locgrdd/.hudson/jobs/SeleniumTest/workspace/results.html
14:57:22.295 INFO – Java: Sun Microsystems Inc. 10.0-b19
14:57:22.297 INFO – OS: Linux 2.6.18-164.10.1.el5 i386
14:57:22.304 INFO – v2.0 [a2], with Core v2.0 [a2]
14:57:22.402 INFO – RemoteWebDriver instances should connect to: http://10.117.130.32:4444/wd/hub
14:57:22.403 INFO – Version Jetty/5.1.x
14:57:22.404 INFO – Started HttpContext[/selenium-server/driver,/selenium-server/driver]
14:57:22.404 INFO – Started HttpContext[/selenium-server,/selenium-server]
14:57:22.404 INFO – Started HttpContext[/,/]
14:57:22.415 INFO – Started org.openqa.jetty.jetty.servlet.ServletHandler@a6d51e
14:57:22.416 INFO – Started HttpContext[/wd,/wd]
14:57:22.418 INFO – Started SocketListener on 0.0.0.0:4444
14:57:22.418 INFO – Started org.openqa.jetty.jetty.Server@1d63e39
14:57:22.461 WARN – It looks like your baseUrl (http://www.bbc.co.uk/weather) is pointing to a file, not a directory (it doesn’t end with a /). We’re going to have to strip off the last part of the pathname.
14:57:22.489 INFO – Preparing Firefox profile…
Error: no display specified
HTML suite exception seen:
java.lang.RuntimeException: Timed out waiting for profile to be created!
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.waitForFullProfileToBeCreated(FirefoxChromeLauncher.java:348)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.populateCustomProfileDirectory(FirefoxChromeLauncher.java:124)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.launch(FirefoxChromeLauncher.java:91)
at org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.launchHTMLSuite(FirefoxChromeLauncher.java:393)
at org.openqa.selenium.server.browserlaunchers.FirefoxLauncher.launchHTMLSuite(FirefoxLauncher.java:94)
at org.openqa.selenium.server.htmlrunner.HTMLLauncher.runHTMLSuite(HTMLLauncher.java:121)
at org.openqa.selenium.server.htmlrunner.HTMLLauncher.runHTMLSuite(HTMLLauncher.java:166)
at org.openqa.selenium.server.SeleniumServer.runHtmlSuite(SeleniumServer.java:545)
at org.openqa.selenium.server.SeleniumServer.boot(SeleniumServer.java:239)
at org.openqa.selenium.server.SeleniumServer.main(SeleniumServer.java:198)
14:57:42.615 INFO – Shutting down…

By: vineet

vineet — Wed, 12 Jan 2011 00:31:05 +0000

Can you run the app via jetty run (see section 1.1 above) and access the app in the browser?

By: Dan

Dan — Tue, 11 Jan 2011 23:52:32 +0000

profile selenium

plugin
groupId org.codehaus.mojo 
artifactId gwt-maven-plugin
 version 2.1.0-1

configuration 
output ${basedir}/war
 webXml ${basedir}/war/WEB-INF/web.xml runTarget index.html
extraJvmArgs
-Dgwt.style=DETAILED -Xmx512M -Xss1024k -XX:MaxPermSize=128m -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl -Dlogback.configurationFile=./src/test/resources/logback-test.xml
bindAddress  0.0.0.0

executions
execution
id start-jetty-server 
phase pre-integration-test
goals
goal run

plugin
groupId org.codehaus.mojo
 artifactId selenium-maven-plugin 
version 1.1

executions
execution
id start  phase pre-integration-test
goals
goal start-server
configuration
background true 
logOutput true

execution
id stop  phase post-integration-test
goals
goal stop-server

By: Dan

Dan — Tue, 11 Jan 2011 23:44:48 +0000

run the app via gwt:run would be a good idea, but when i launch it in Jetty, gwt development mode window pop up and stuck there, the following selenium server didn't start, no to mention the selenium test. here is my pom.xml: selenium org.codehaus.mojo gwt-maven-plugin 2.1.0-1 ${basedir}/war ${basedir}/war/WEB-INF/web.xml index.html -Dgwt.style=DETAILED -Xmx512M -Xss1024k -XX:MaxPermSize=128m -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl -Dlogback.configurationFile=./src/test/resources/logback-test.xml 0.0.0.0 start-jetty-server pre-integration-test run org.codehaus.mojo selenium-maven-plugin 1.1 start pre-integration-test start-server true true stop post-integration-test stop-server ... do you have any idea what might goes wrong? thanks!