Integration testing involves the testing of larger segments of your Tapestry

...

module or web application, typically including the user interface.

The Tapestry Test Utilities is a small library This library is just a couple of base classes to make it easier to build integration test suites around Selenium.This library is currently based on Selenium 0.8.1 version 2.14.0.

The strategy is to start, in-process, a Selenimum Selenium Server (which, in turn, starts and manages a web browser), a Jetty instance (for the web browser to talk to), and a Selenium client (which talks to the server).

The client is able to request URLs, fill in form data, click links, and make assertions about output and behavior.

Usage

...

The core part of this library is a base class for you to extend your tests cases fromclasses : AbstractIntegrationTestSuite SeleniumTestCase.

This class is responsible for starting an instance of Jetty to server your web application, as well as a copy of Selenium Server. It also implements the Selenium interface.You must inform the suite about the location of your web application. The default location is src/main/webapp (as this is the default directory for storing a web application when building using Maven). This can be changed by provided a public constructor for your test suite.

Note
Before Tapestry 5.2, your class should extend AbstractIntegrationTestSuite

Here's an example from one of the Tapestry modules:

Code Block
language java title Your Integration Test Class : SinglePersistenceUnitIntegrationTest.java
No Format
package org.apache.tapestry5.jpa.integration.springapp2; import org.apache.tapestry5.test.AbstractIntegrationTestSuiteSeleniumTestCase; import org.testng.annotations.Test; public class TapestrySpringIntegrationTestSinglePersistenceUnitIntegrationTest extends AbstractIntegrationTestSuiteSeleniumTestCase { public TapestrySpringIntegrationTest() { super("src/test/webapp"); } @Test public void integrationpersist_testentities() throws Exception { open(BASE_URL); type("input", "paris in the springtime("/persistitem"); clickAndWaitassertEquals(getText("//inputspan[@value@id='Convertname']"); assertFieldValue("input", "PARIS IN THE SPRINGTIME"); }.length(), 0); @Test public void access_to_spring_context() throws Exception { open(BASE_URLclickAndWait("link=create item"); assertTextPresentassertText("[upcase]//span[@id='name']", "name"); } }

With the SeleniumTestCase class, you can use basic This is a very simple example, and demonstrates a mix of Selenium methods (such as open() and type()) and methods added by the AbstractIntegrationTestSuite SeleniumTestCase base class (clickAndWait() and assertFieldValue()).

Of course, a real integration test would contain many methods, and may need to single thread their execution, or even specify an execution order.

In addition, the AbstractIntegrationTestSuite SeleniumTestCase base class extends the normal exception reporting provided by Selenium; when a failure occurs inside Selenium server, a more detailed message, including the current page's HTML source, is reported to System.err.

Configuration

All the configuration of your Integration Tests should be in your testng.xml file. Tapestry provides some parameters, in order to have the right environment for your tests.

...

Here's an example :

<suite name="Selenium Tests Suite" annotations="1.5">
  <test name="Integration Tests" enabled="true">
    <parameter name="tapestry.browser-start-command" value="*googlechrome" />
    <parameter name="tapestry.port" value="9091" />

    <classes>
      <class name="com.example.newapp.SeleniumTest"></class>
    </classes>
  </test>
</suite>

Some Interesting Tools

Here are some interesting plugins you can use to write your integration tests.

• Google Chrome : xpathOnClick
• FireFox : Selenium IDE

...

...