Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2
    • Component/s: Quality Assurance
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-13814Run the smoke tests on the grid
      KULRICE-8150Upgrade Selenium 1 Smoke Tests to Selenium 2 (WebDriver)
      KULRICE-5603Selenium Smoke Test Creation: Identity Maintenance Documents Tests
      KULRICE-13838KRAD Kitchen Sink Selenium Smoke tests
      KULRICE-5602Selenium Smoke Test Creation: Identity Create Documents Tests
      KULRICE-5604Selenium Smoke Test Creation: Configuration Create Documents Tests
      KULRICE-5605Selenium Smoke Test Creation: Configuration Maintenance Documents Tests
      KULRICE-5606Selenium Smoke Test Creation: Workflow Create Documents Tests
      KULRICE-5607Selenium Smoke Test Creation: Workflow Maintenance Documents Tests
      KULRICE-5608Selenium Smoke Test Creation: Main Menu Create Documents Tests
    • Rice Team:
      QA
    • Rice Module:
      Rice Core
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      the nightly smoke tests are failing and it's noted in the log that the connection to the selenium server is being refused? not sure if it's on the server side or how the tests are configured though?

      ire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
      	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
      	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
      	at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:172)
      	at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:104)
      	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70)
      testEditRouteRules(edu.samplu.mainmenu.test.WorkFlowRouteRulesIT)  Time elapsed: 0.002 sec  <<< ERROR!
      java.lang.RuntimeException: Could not contact Selenium Server; have you started it on 'localhost:4444' ?
      Read more at http://seleniumhq.org/projects/remote-control/not-started.html
      Connection refused
      	at com.thoughtworks.selenium.DefaultSelenium.start(DefaultSelenium.java:102)
      	at edu.samplu.mainmenu.test.WorkFlowRouteRulesIT.setUp(WorkFlowRouteRulesIT.java:39)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
      	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
      	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
      	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
      	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
      	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
      	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
      	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
      	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
      	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
      	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
      	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
      	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
      	at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
      	at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
      	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
      	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
      	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
      	at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:172)
      	at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:104)
      	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70)

        Issue Links

          Activity

          Hide
          Erik Meade added a comment -

          I added a shell command to the top of the build to set export DISPLAY=:7055 I can see (both export DISPLAYs) run but still getting the 7055 port error. Googling I found which mentions using the envInject plugin to set, which I've done and am running now.

          https://groups.google.com/group/jenkinsci-users/tree/browse_frm/month/2012-02/5ec694983e0c7186?rnum=91&lnk=ol&pli=1

          With envInject plugin you can export the DISPLAY variable in the prebuild 
          step of any build from jenkins. You can set it to the xvfb screen the 
          latter will use (you can specify one manually with advanced config of xvfb 
          plugin). 
          
          Show
          Erik Meade added a comment - I added a shell command to the top of the build to set export DISPLAY=:7055 I can see (both export DISPLAYs) run but still getting the 7055 port error. Googling I found which mentions using the envInject plugin to set, which I've done and am running now. https://groups.google.com/group/jenkinsci-users/tree/browse_frm/month/2012-02/5ec694983e0c7186?rnum=91&lnk=ol&pli=1 With envInject plugin you can export the DISPLAY variable in the prebuild step of any build from jenkins. You can set it to the xvfb screen the latter will use (you can specify one manually with advanced config of xvfb plugin).
          Hide
          Erik Meade added a comment - - edited

          Using the envInject we get a new error, now it looks like xvfb isn't listening on 7055, but 20. The text above says the port can be set in the xvfb plugin advanced config.

          [INFO] Starting Xvfb...
          [INFO] Using display: :20
          ...
          Caused by: org.openqa.selenium.firefox.NotConnectedException: Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms. Firefox console output:
          Error: cannot open display: :7055
          Error: cannot open display: :7055
          
          Show
          Erik Meade added a comment - - edited Using the envInject we get a new error, now it looks like xvfb isn't listening on 7055, but 20. The text above says the port can be set in the xvfb plugin advanced config. [INFO] Starting Xvfb... [INFO] Using display: :20 ... Caused by: org.openqa.selenium.firefox.NotConnectedException: Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms. Firefox console output: Error: cannot open display: :7055 Error: cannot open display: :7055
          Hide
          Erik Meade added a comment -

          But, I'll set the DISPLAY to :20

          Show
          Erik Meade added a comment - But, I'll set the DISPLAY to :20
          Hide
          Erik Meade added a comment -

          The smoke tests are running. Seeing assertion errors.

          Show
          Erik Meade added a comment - The smoke tests are running. Seeing assertion errors.
          Hide
          Erik Meade added a comment -
          
          java.lang.AssertionError: Exception in setUp Failed to connect to binary FirefoxBinary(/usr/local/bin/firefox) on port 7055; process output follows: 
          Xlib:  extension "RANDR" missing on display ":20".
          *** LOG addons.manager: Application has been upgraded
          *** LOG addons.xpi: startup
          *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous5512443836862362620webdriver-profile/extensions/webdriver-staging
          *** LOG addons.xpi: checkForChanges
          *** LOG addons.xpi: Opening database
          *** LOG addons.xpi: Creating database schema
          *** LOG addons.xpi: New add-on fxdriver@googlecode.com installed in app-profile
          *** LOG addons.xpi: New add-on {972ce4c6-7e08-4474-a285-3208198ce6fd} installed in app-global
          *** LOG addons.xpi: Updating database with changes to installed add-ons
          *** LOG addons.xpi: Updating add-on states
          *** LOG addons.xpi: Writing add-ons list
          *** LOG addons.xpi: shutdown
          
          
          Show
          Erik Meade added a comment - java.lang.AssertionError: Exception in setUp Failed to connect to binary FirefoxBinary(/usr/local/bin/firefox) on port 7055; process output follows: Xlib: extension "RANDR" missing on display ":20" . *** LOG addons.manager: Application has been upgraded *** LOG addons.xpi: startup *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous5512443836862362620webdriver-profile/extensions/webdriver-staging *** LOG addons.xpi: checkForChanges *** LOG addons.xpi: Opening database *** LOG addons.xpi: Creating database schema *** LOG addons.xpi: New add-on fxdriver@googlecode.com installed in app-profile *** LOG addons.xpi: New add-on {972ce4c6-7e08-4474-a285-3208198ce6fd} installed in app-global *** LOG addons.xpi: Updating database with changes to installed add-ons *** LOG addons.xpi: Updating add-on states *** LOG addons.xpi: Writing add-ons list *** LOG addons.xpi: shutdown

            People

            • Assignee:
              Erik Meade
              Reporter:
              Erik Meade
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel