Clever Geek Handbook

Selenium testing in Hudson's question

I am having trouble running a simple selenium test through Hudson.

I installed the SeleniumHQ plugin for Hudson and set up a job to run a simple test suite that consists of two tests that work fine with the Selenium IDE and the TestNG plugin in Eclipse.

However, when I try to run them through Hudson, the testing just gets delayed at the end of the first test (no matter what test it is, I've tried many different ones that all work when run in other enviornments).

The console output from Hudson looks like this:

11: 48: 09.543 INFO - Java: Sun Microsystems Inc. 14.2-b01
11: 48: 09.544 INFO - OS: Windows Vista 6.0 x86
11: 48: 09.559 INFO - v1.0.1 [2696], with Core v @ VERSION @ [@ REVISION @ ]
11: 48: 09.655 INFO - Version Jetty / 5.1.x
11: 48: 09.656 INFO - Started HttpContext [/ selenium-server / driver, / selenium-server / driver]
11: 48: 09.657 INFO - Started HttpContext [/ selenium-server, / selenium-server]
11: 48: 09.657 INFO - Started HttpContext [/, /]
11: 48: 09.670 INFO - Started SocketListener on 0.0.0.0:4444
11: 48: 09.670 INFO - Started org.mortbay.jetty.Server@c40c80
11: 48: 09.825 INFO - Preparing Firefox profile ...
11: 48: 12.046 INFO - Launching Firefox ...
11: 48: 12.919 INFO - Checking Resource aliases

Strangely, I see that the first test is running and it passes, but the selenium then doesn't advance to the next, and if I create a test suite with only one test, it just hangs there indefinitely. Note that I have an action AssertVisible

in the test to validate the results. Do I need to return anything else for Hudson to run the test correctly?

Thanks in advance for any help on this ...

+2


source to share


3 answers


Could you check if the command line specified by the SeleniumHQ plugin is correct?



  • In the command window paste the command and run it
  • Verify that starting, executing, and ending the test normally
  • Check results file
0


source


I had this problem. You can get around this by installing compatible versions of selenium and firefox. See if they work together outside of Hudson.



0


source


The problem arises because you provided the TestCase

file, use it TestSuite html file

for testing instead .

After registering the script in seleniumhq, select save TestSuite as the menu to save as TestSuite.

0


source






More articles:


All Articles