com.thoughtworks.selenium.SeleniumException: Timed out after 15000ms

Jenkins JIRA | mjstrecker | 7 years ago
  1. 0

    We have the project setup to display Junit test results by checking the setting : Publish JUnit test result report. The testsuite in the generated test result xml is ignored when displaying the test results for the project. Here is the situation, we run Selenium tests for IE and FF ... so the same tests run twice. Hudson correctly displays the fact the these tests ran twice, but it's impossible to know if the tests were IE or FF because the testsuite isn't displayed. Here are the two XML files : {code} <?xml version="1.0" encoding="UTF-8"?> <testsuite name="Firefox" failures="0" tests="5" time="55.688" errors="0"> <properties/> <testcase name="testBogusLogin" time="3.406" classname="mypackage.selenium.TestLoginPage"/> <testcase name="testLogin" time="2.469" classname="mypackage.selenium.TestLoginPage"/> <testcase name="testLoginBadPassword" time="3.375" classname="mypackage.selenium.TestLoginPage"/> <testcase name="testMenu" time="32.86" classname="mypackage.selenium.TestMenu"/> </testsuite> {code} {code} <?xml version="1.0" encoding="UTF-8"?> <testsuite name="IE" failures="2" tests="5" time="60.047" errors="0"> <properties/> <testcase name="testBogusLogin" time="3.875" classname="mypackage.selenium.TestLoginPage"/> <testcase name="testLogin" time="15.89" classname="mypackage.selenium.TestLoginPage"> <failure type="com.thoughtworks.selenium.SeleniumException" message="Timed out after 15000ms"> <![CDATA[com.thoughtworks.selenium.SeleniumException: Timed out after 15000ms at com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97) at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91) at com.thoughtworks.selenium.DefaultSelenium.waitForPageToLoad(DefaultSelenium.java:635) at mypackage.selenium.SeleniumTestNgBase.waitForPageToLoad(Unknown Source) at mypackage.selenium.SeleniumTestNgBase.waitForPageToLoad(Unknown Source) at mypackage.selenium.TestLoginPage.testLogin(Unknown Source) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) ... Removed 7 stack frames]]> </failure> </testcase> <testcase name="testLoginBadPassword" time="3.843" classname="mypackage.selenium.TestLoginPage"/> <testcase name="testMenu" time="25.969" classname="mypackage.selenium.TestMenu"> <failure type="com.thoughtworks.selenium.SeleniumException" message="Timed out after 15000ms"> <![CDATA[com.thoughtworks.selenium.SeleniumException: Timed out after 15000ms at com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97) at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91) at com.thoughtworks.selenium.DefaultSelenium.waitForPageToLoad(DefaultSelenium.java:635) at mypackage.selenium.SeleniumTestNgBase.waitForPageToLoad(Unknown Source) at mypackage.selenium.SeleniumTestNgBase.waitForPageToLoad(Unknown Source) at mypackage.selenium.TestMenu.testMenu(Unknown Source) ... Removed 22 stack frames]]> </failure> </testcase> </testsuite> {code}

    Jenkins JIRA | 7 years ago | mjstrecker
    com.thoughtworks.selenium.SeleniumException: Timed out after 15000ms
  2. 0

    We have the project setup to display Junit test results by checking the setting : Publish JUnit test result report. The testsuite in the generated test result xml is ignored when displaying the test results for the project. Here is the situation, we run Selenium tests for IE and FF ... so the same tests run twice. Hudson correctly displays the fact the these tests ran twice, but it's impossible to know if the tests were IE or FF because the testsuite isn't displayed. Here are the two XML files : {code} <?xml version="1.0" encoding="UTF-8"?> <testsuite name="Firefox" failures="0" tests="5" time="55.688" errors="0"> <properties/> <testcase name="testBogusLogin" time="3.406" classname="mypackage.selenium.TestLoginPage"/> <testcase name="testLogin" time="2.469" classname="mypackage.selenium.TestLoginPage"/> <testcase name="testLoginBadPassword" time="3.375" classname="mypackage.selenium.TestLoginPage"/> <testcase name="testMenu" time="32.86" classname="mypackage.selenium.TestMenu"/> </testsuite> {code} {code} <?xml version="1.0" encoding="UTF-8"?> <testsuite name="IE" failures="2" tests="5" time="60.047" errors="0"> <properties/> <testcase name="testBogusLogin" time="3.875" classname="mypackage.selenium.TestLoginPage"/> <testcase name="testLogin" time="15.89" classname="mypackage.selenium.TestLoginPage"> <failure type="com.thoughtworks.selenium.SeleniumException" message="Timed out after 15000ms"> <![CDATA[com.thoughtworks.selenium.SeleniumException: Timed out after 15000ms at com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97) at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91) at com.thoughtworks.selenium.DefaultSelenium.waitForPageToLoad(DefaultSelenium.java:635) at mypackage.selenium.SeleniumTestNgBase.waitForPageToLoad(Unknown Source) at mypackage.selenium.SeleniumTestNgBase.waitForPageToLoad(Unknown Source) at mypackage.selenium.TestLoginPage.testLogin(Unknown Source) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) ... Removed 7 stack frames]]> </failure> </testcase> <testcase name="testLoginBadPassword" time="3.843" classname="mypackage.selenium.TestLoginPage"/> <testcase name="testMenu" time="25.969" classname="mypackage.selenium.TestMenu"> <failure type="com.thoughtworks.selenium.SeleniumException" message="Timed out after 15000ms"> <![CDATA[com.thoughtworks.selenium.SeleniumException: Timed out after 15000ms at com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97) at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91) at com.thoughtworks.selenium.DefaultSelenium.waitForPageToLoad(DefaultSelenium.java:635) at mypackage.selenium.SeleniumTestNgBase.waitForPageToLoad(Unknown Source) at mypackage.selenium.SeleniumTestNgBase.waitForPageToLoad(Unknown Source) at mypackage.selenium.TestMenu.testMenu(Unknown Source) ... Removed 22 stack frames]]> </failure> </testcase> </testsuite> {code}

    Jenkins JIRA | 7 years ago | mjstrecker
    com.thoughtworks.selenium.SeleniumException: Timed out after 15000ms
  3. 0

    [JENKINS-6014] Test Suite Not Displayed in Test Results - Jenkins JIRA

    jenkins-ci.org | 6 months ago
    com.thoughtworks.selenium.SeleniumException: Timed out after 15000ms
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Not able to run script in IE

    Google Groups | 6 years ago | rajkumar agrawal
    com.thoughtworks.selenium.SeleniumException: Timed out after 45000ms
  6. 0

    Software Functional Test Automation: DataProvider - Data Driven Testing with Selenium and TestNG

    blogspot.com | 2 months ago
    com.thoughtworks.selenium.SeleniumException: Timed out after 30000ms

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.thoughtworks.selenium.SeleniumException

      Timed out after 15000ms

      at com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError()
    2. selenium-java
      DefaultSelenium.waitForPageToLoad
      1. com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97)
      2. com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91)
      3. com.thoughtworks.selenium.DefaultSelenium.waitForPageToLoad(DefaultSelenium.java:635)
      3 frames
    3. mypackage.selenium
      TestLoginPage.testLogin
      1. mypackage.selenium.SeleniumTestNgBase.waitForPageToLoad(Unknown Source)
      2. mypackage.selenium.SeleniumTestNgBase.waitForPageToLoad(Unknown Source)
      3. mypackage.selenium.TestLoginPage.testLogin(Unknown Source)
      3 frames
    4. Java RT
      Thread.run
      1. java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
      2. java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
      3. java.util.concurrent.FutureTask.run(FutureTask.java:123)
      4. java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
      5. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
      6. java.lang.Thread.run(Thread.java:595)
      6 frames