Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-b1, 2.0
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-4908Fix CI environment emails
      KULRICE-241Write unit tests in PHP and/or other technologies to be run in our CI environment to ensure technology interoperability
      KULRICE-8150Upgrade Selenium 1 Smoke Tests to Selenium 2 (WebDriver)
      KULRICE-14260Continuous Deployment: CI PoC for the testing and auto merging
      KULRICE-12819Transition 2.5 integration test CI jobs
      KULRICE-8695Bitronix integration test failures in CI
      KULRICE-7102Create an integration test for the action list service
      KULRICE-6669Create dev branch & ci jobs for unit and integration tests
      KULRICE-4116CI test are failing intermittently
      KULRICE-5665Implement the ability to run rice sample app as a seperate application integrated with the Rice Standalone Server, put process in place to automatically deploy to a test environment using CI
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Once the selenium tests are checked into svn, work with Matt (and Mayank/Viral) to figure out how to run them in CI. Jenkins has a Selenium Grid plugin (https://wiki.jenkins-ci.org/display/JENKINS/Selenium+Plugin). There's also Sauce Labs (http://saucelabs.com/) which provides drivers for running selenium tests, but I'm not sure how it integrates into Jenkins.

      KFS is running selenium tests in CI via Hudson/Jenkins as far as I understand, so it would be good to discuss with Jonathan Keller how they do it.

      Once an approach is decided on, it should be run by the team leads for review before implementing.

        Issue Links

          Activity

          Hide
          Jessica Coltrin (Inactive) added a comment -

          This task must be complete prior to this one.

          Show
          Jessica Coltrin (Inactive) added a comment - This task must be complete prior to this one.
          Hide
          Leo Przybylski (Inactive) added a comment -
          • Selenium tests will be Junit4/Webdriver tests.
          • rice/sampleapp is where the selenium tests will live.
          • rice/sampleapp is going to be modified to distribute a test-jar containing the selenium tests
          • The selenium plugin will be installed in the rice/deploy module. It will not run during any phase automatically.
          • rice/deploy will have a "selenium-test" goal.
          • rice/deploy uses the "wait-for-tomcat-startup" execution to verify tomcat has started on http://dev.rice.kuali.org
          • After "wait-for-tomcat-startup", "selenium-test" will run in rice/deploy against http://dev.rice.kuali.org.
          • The url http://dev.rice.kuali.org will be configurable via system property in the selenium test, but will be maintained as a maven property.
          Show
          Leo Przybylski (Inactive) added a comment - Selenium tests will be Junit4/Webdriver tests. rice/sampleapp is where the selenium tests will live. rice/sampleapp is going to be modified to distribute a test-jar containing the selenium tests The selenium plugin will be installed in the rice/deploy module. It will not run during any phase automatically. rice/deploy will have a "selenium-test" goal. rice/deploy uses the "wait-for-tomcat-startup" execution to verify tomcat has started on http://dev.rice.kuali.org After "wait-for-tomcat-startup", "selenium-test" will run in rice/deploy against http://dev.rice.kuali.org . The url http://dev.rice.kuali.org will be configurable via system property in the selenium test, but will be maintained as a maven property.
          Hide
          Travis Schneeberger added a comment -

          Leo,

          Currently the selenium tests are in the src/it/java folder. This folder is a semi-standard place to put integration tests but is not fully supported by maven (from my understanding).

          In the branch where I was doing my groovy-eclipse-compiler work (https://test.kuali.org/svn/rice/sandbox/KULRICE-5640) I included a build-helper plugin to add source folders. I think it is still beneficial to keep the selenium tests out of the traditional src/test folders since those are generally for "unit" tests. See the following snippet:

                  <plugin>
                    <groupId>org.codehaus.mojo</groupId>
                    <artifactId>build-helper-maven-plugin</artifactId>
                    <version>1.7</version>
                    <executions>
                      <execution>
                        <id>add-source</id>
                        <phase>initialize</phase>
                        <goals>
                          <goal>add-source</goal>
                        </goals>
                        <configuration>
                          <sources>
                            <!-- these src dirs don't have to be added in version 2.5.2 of groovy-eclipse-compiler -->
                            <source>src/main/java</source>
                            <source>src/main/groovy</source>
                          </sources>
                        </configuration>
                      </execution>
                      <execution>
                        <id>add-test-source</id>
                        <phase>initialize</phase>
                        <goals>
                          <goal>add-test-source</goal>
                        </goals>
                        <configuration>
                          <sources>
                            <!-- these src dirs don't have to be added in version 2.5.2 of groovy-eclipse-compiler -->
                            <source>src/test/java</source>
                            <source>src/test/groovy</source>
                            <!-- integration tests (they still need to be added since they are non-standard maven dirs -->
                            <source>src/it/java</source>
                            <source>src/it/groovy</source>
                          </sources>
                        </configuration>
                      </execution>
                    </executions>
                  </plugin>
          
          Show
          Travis Schneeberger added a comment - Leo, Currently the selenium tests are in the src/it/java folder. This folder is a semi-standard place to put integration tests but is not fully supported by maven (from my understanding). In the branch where I was doing my groovy-eclipse-compiler work ( https://test.kuali.org/svn/rice/sandbox/KULRICE-5640 ) I included a build-helper plugin to add source folders. I think it is still beneficial to keep the selenium tests out of the traditional src/test folders since those are generally for "unit" tests. See the following snippet: <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>build-helper-maven-plugin</artifactId> <version>1.7</version> <executions> <execution> <id>add-source</id> <phase>initialize</phase> <goals> <goal>add-source</goal> </goals> <configuration> <sources> <!-- these src dirs don't have to be added in version 2.5.2 of groovy-eclipse-compiler --> <source>src/main/java</source> <source>src/main/groovy</source> </sources> </configuration> </execution> <execution> <id>add-test-source</id> <phase>initialize</phase> <goals> <goal>add-test-source</goal> </goals> <configuration> <sources> <!-- these src dirs don't have to be added in version 2.5.2 of groovy-eclipse-compiler --> <source>src/test/java</source> <source>src/test/groovy</source> <!-- integration tests (they still need to be added since they are non-standard maven dirs --> <source>src/it/java</source> <source>src/it/groovy</source> </sources> </configuration> </execution> </executions> </plugin>
          Hide
          Rice-CI User (Inactive) added a comment -

          Integrated in rice-trunk-nightly #196 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/196/)
          KULRICE-5613 Fixing compile error
          KULRICE-5613 clicking logout link
          KULRICE-5613 adding login logout
          KULRICe-5613 fixing url
          KULRICE-5613 fixing url
          KULRICE-5613 checking in changes to use system property for selenium tests
          KULRICE-5613 checking in changes to use system property for selenium tests

          Show
          Rice-CI User (Inactive) added a comment - Integrated in rice-trunk-nightly #196 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/196/ ) KULRICE-5613 Fixing compile error KULRICE-5613 clicking logout link KULRICE-5613 adding login logout KULRICe-5613 fixing url KULRICE-5613 fixing url KULRICE-5613 checking in changes to use system property for selenium tests KULRICE-5613 checking in changes to use system property for selenium tests
          Hide
          Rice-CI User (Inactive) added a comment -

          Integrated in rice-trunk-nightly #201 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/201/)
          KULRICE-5613 - Give the plugin execution that resets the remote server an id
          KULRICE-5613 - config file for the remote instance Selenium executes against
          KULRICE-5675 - ec2 + Amazon RDS environments are up
          KULRICE-5613 - Selenium tests run against new enviroment

          Show
          Rice-CI User (Inactive) added a comment - Integrated in rice-trunk-nightly #201 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/201/ ) KULRICE-5613 - Give the plugin execution that resets the remote server an id KULRICE-5613 - config file for the remote instance Selenium executes against KULRICE-5675 - ec2 + Amazon RDS environments are up KULRICE-5613 - Selenium tests run against new enviroment
          Hide
          Rice-CI User (Inactive) added a comment -

          Integrated in rice-trunk-nightly #202 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/202/)
          KULRICE-5675 KULRICE-5613 simpler config
          KULRICE-5675 KULRICE-5613 environment configuration

          Show
          Rice-CI User (Inactive) added a comment - Integrated in rice-trunk-nightly #202 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/202/ ) KULRICE-5675 KULRICE-5613 simpler config KULRICE-5675 KULRICE-5613 environment configuration
          Hide
          Rice-CI User (Inactive) added a comment -

          Integrated in rice-trunk-nightly #203 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/203/)
          KULRICE-5675 KULRICE-5613 Frienlier DNS names
          KULRICE-5613 - Config cleanup

          Show
          Rice-CI User (Inactive) added a comment - Integrated in rice-trunk-nightly #203 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/203/ ) KULRICE-5675 KULRICE-5613 Frienlier DNS names KULRICE-5613 - Config cleanup
          Hide
          Jeff Caddel (Inactive) added a comment -

          Smoke test runs after the junit tests pass. See:
          http://ci.rice.kuali.org/view/Rice%20Trunk/job/rice-trunk-smoke-test/

          Show
          Jeff Caddel (Inactive) added a comment - Smoke test runs after the junit tests pass. See: http://ci.rice.kuali.org/view/Rice%20Trunk/job/rice-trunk-smoke-test/
          Hide
          Jessica Coltrin (Inactive) added a comment -

          Closing since these items are now in the release notes.

          Show
          Jessica Coltrin (Inactive) added a comment - Closing since these items are now in the release notes.

            People

            • Assignee:
              Jeff Caddel (Inactive)
              Reporter:
              Matt Sargent
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel