com.github.bordertech.wcomponents.test.example

Class ExampleSeleniumTest

java.lang.Object

com.github.bordertech.wcomponents.test.selenium.WComponentSeleniumTestCase

com.github.bordertech.wcomponents.test.example.ExampleSeleniumTest

Direct Known Subclasses:

ExampleMultiBrowserSeleniumTest

public class ExampleSeleniumTest
extends WComponentSeleniumTestCase

This class is an example showing various ways of testing a WComponent UI using Selenium. The same UI is tested multiple times using different approaches.

Since:

1.0.0

Author:

Yiannis Paschalidis

Constructor Summary

Constructors

Constructor and Description
ExampleSeleniumTest() Creates a ExampleSeleniumTest.

Method Summary

Modifier and Type	Method and Description
void	testDuplicatorWithGettersWComponentImpl() This test implementation uses ByWComponent to find the HTML controls.
void	testDuplicatorWithGettersWComponentPathImpl() This test implementation uses ByWComponentPath to find the HTML controls.
void	testDuplicatorWithNoGettersHtmlImpl() This test implementation uses a 'traditional' Selenium approach, matching on HTML elements.
void	testDuplicatorWithNoGettersWComponentPathImpl() This test implementation uses ByWComponentPath to find the HTML controls.

Methods inherited from class com.github.bordertech.wcomponents.test.selenium.WComponentSeleniumTestCase

getDriver, getDriverId, getDriverType, getDriverWithoutLaunching, getUrl, getUserContextForSession, releaseDriver, setDriver, setUrl

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

ExampleSeleniumTest

public ExampleSeleniumTest()

Creates a ExampleSeleniumTest. The WComponent which is passed to the superclass's constructor is the UI to be tested. Small sections of application code may need to be wrapped in a shell which puts them in the correct state.

Method Detail

testDuplicatorWithNoGettersWComponentPathImpl

public void testDuplicatorWithNoGettersWComponentPathImpl()

This test implementation uses ByWComponentPath to find the HTML controls. A ByWComponentPath is built using a full or partial set of classes which describe a path through the WComponent Tree structure. This is the preferred method of testing WComponent UIs, as it should be stable between releases, and does not require applications to expose UI structure via getters. The UI structure tree structure used in this example is as follows:

    ExampleUI
       WTabSet
          WTab
            TextDuplicator
              WTextField
              WButton
              WButton
          WTab
            TextDuplicatorWithGetters
              WTextField
              WButton
              WButton
 

So to obtain the first WTextField, any of the following paths could be used:

Full path, including tab index

ExampleUI/WTabSet/WTab[0]/ExampleSeleniumTest$TextDuplicator/WTextField

Full path, minus tab index (first tab is used)

ExampleUI/WTabSet/WTab/ExampleSeleniumTest$TextDuplicator/WTextField

First text field in a TextDuplicator

ExampleSeleniumTest$TextDuplicator/WTextField

First text field in the first tab

WTab/WTextField

First text field in the whole UI

WTextField

The amount of detail you will need to specify for the paths in your tests will depend on how your UI is structured. If you have created reusable application components (e.g. a "NamePanel"), you will be able to match on this directly in the path rather than having to look for the WComponent[x]/WComponent[y]/WComponent[z].

testDuplicatorWithNoGettersHtmlImpl

public void testDuplicatorWithNoGettersHtmlImpl()

This test implementation uses a 'traditional' Selenium approach, matching on HTML elements. This method should not generally be used for testing WComponent applications, as the HTML output can change without notice between different theme versions; the rendered HTML is transform-dependant, not WComponent-dependant.

testDuplicatorWithGettersWComponentPathImpl

public void testDuplicatorWithGettersWComponentPathImpl()

This test implementation uses ByWComponentPath to find the HTML controls. See testDuplicatorWithNoGettersWComponentPathImpl() for an explanation of how the paths function.

testDuplicatorWithGettersWComponentImpl

public void testDuplicatorWithGettersWComponentImpl()

This test implementation uses ByWComponent to find the HTML controls. This is the easiest approach to use, but requires that the UI being tested has been built with getters for every control, which is not usually practical.