Docs Help

Terms, Icons, and Labels

Many classes have shortcut names used when creating (instantiating) a class with a configuration object. The shortcut name is referred to as an alias (or xtype if the class extends Ext.Component). The alias/xtype is listed next to the class name of applicable classes for quick reference.

Access Levels

Framework classes or their members may be specified as private or protected. Else, the class / member is public. Public, protected, and private are access descriptors used to convey how and when the class or class member should be used.

Member Types

Member Syntax

Below is an example class member that we can disect to show the syntax of a class member (the lookupComponent method as viewed from the Ext.button.Button class in this case).

lookupComponent ( item ) : Ext.Component
protected

Called when a raw config object is added to this container either during initialization of the items config, or when new items are added), or {@link #insert inserted.

This method converts the passed object into an instanced child component.

This may be overridden in subclasses when special processing needs to be applied to child creation.

Parameters

item :  Object

The config object being added.

Returns
Ext.Component

The component to be added.

Let's look at each part of the member row:

Member Flags

The API documentation uses a number of flags to further commnicate the class member's function and intent. The label may be represented by a text label, an abbreviation, or an icon.

Class Icons

- Indicates a framework class

- A singleton framework class. *See the singleton flag for more information

- A component-type framework class (any class within the Ext JS framework that extends Ext.Component)

- Indicates that the class, member, or guide is new in the currently viewed version

Member Icons

- Indicates a class member of type config

- Indicates a class member of type property

- Indicates a class member of type method

- Indicates a class member of type event

- Indicates a class member of type theme variable

- Indicates a class member of type theme mixin

- Indicates that the class, member, or guide is new in the currently viewed version

Class Member Quick-Nav Menu

Just below the class name on an API doc page is a row of buttons corresponding to the types of members owned by the current class. Each button shows a count of members by type (this count is updated as filters are applied). Clicking the button will navigate you to that member section. Hovering over the member-type button will reveal a popup menu of all members of that type for quick navigation.

Getter and Setter Methods

Getting and setter methods that correlate to a class config option will show up in the methods section as well as in the configs section of both the API doc and the member-type menus just beneath the config they work with. The getter and setter method documentation will be found in the config row for easy reference.

History Bar

Your page history is kept in localstorage and displayed (using the available real estate) just below the top title bar. By default, the only search results shown are the pages matching the product / version you're currently viewing. You can expand what is displayed by clicking on the button on the right-hand side of the history bar and choosing the "All" radio option. This will show all recent pages in the history bar for all products / versions.

Within the history config menu you will also see a listing of your recent page visits. The results are filtered by the "Current Product / Version" and "All" radio options. Clicking on the button will clear the history bar as well as the history kept in local storage.

If "All" is selected in the history config menu the checkbox option for "Show product details in the history bar" will be enabled. When checked, the product/version for each historic page will show alongside the page name in the history bar. Hovering the cursor over the page names in the history bar will also show the product/version as a tooltip.

Search and Filters

Both API docs and guides can be searched for using the search field at the top of the page.

On API doc pages there is also a filter input field that filters the member rows using the filter string. In addition to filtering by string you can filter the class members by access level, inheritance, and read only. This is done using the checkboxes at the top of the page.

The checkbox at the bottom of the API class navigation tree filters the class list to include or exclude private classes.

Clicking on an empty search field will show your last 10 searches for quick navigation.

API Doc Class Metadata

Each API doc page (with the exception of Javascript primitives pages) has a menu view of metadata relating to that class. This metadata view will have one or more of the following:

Expanding and Collapsing Examples and Class Members

Runnable examples (Fiddles) are expanded on a page by default. You can collapse and expand example code blocks individually using the arrow on the top-left of the code block. You can also toggle the collapse state of all examples using the toggle button on the top-right of the page. The toggle-all state will be remembered between page loads.

Class members are collapsed on a page by default. You can expand and collapse members using the arrow icon on the left of the member row or globally using the expand / collapse all toggle button top-right.

Desktop -vs- Mobile View

Viewing the docs on narrower screens or browsers will result in a view optimized for a smaller form factor. The primary differences between the desktop and "mobile" view are:

Viewing the Class Source

The class source can be viewed by clicking on the class name at the top of an API doc page. The source for class members can be viewed by clicking on the "view source" link on the right-hand side of the member row.

GXT 3.x


top

Getting Started with GWT Driver

GWT bindings for Selenium WebDriver.

Reference

Browser testing in GWT

GwtDriver brings GWT support to WebDriver tests. We do this by exposing a few type details from the running application and letting the tests ask questions of the structure of the widgets, rather than forcing them to rely on just the DOM structure, CSS classes, or element IDs. This way, you can write the application and the tests separatly, without either becoming dependent on the structure and expectations of the other.

When you test a screen in an application, you usually don't look at the DOM structure and locate an element with the right ID or XPATH before you click it, but instead rely on the text content or other nearby (usually parent or sibling) widgets. The gwt-driver project tries to encourage WebDriver tests that are structure and landmark based. This has the result of writing tests that are more easily maintained, and easier to refactor and reuse as the application continues to grow.

Concept

The basic idea is to refer to models that describe the widgets in the application, rather that the dom elements themselves. It is still possible (and often necessary) to refer to those elements, but for the most part this is only needed for specific one-off features that don't make sense to build into the models themselves.

Models all extend from org.senchalabs.gwt.gwtdriver.models.GwtWidget. They have a few paths from there:

  • Decorated with org.senchalabs.gwt.gwtdriver.models.GwtWidget.ForWidget, indicating the gwt Widget type that they should represent. Useful for various assertions.
  • Specify a GwtWidgetFinder in their generics, describing the common ways that this widget can be found in a parent. More on this below in Finders.

Locating Widgets

Module configuration

The GWT project will need an additional library used during compile to use the GWT Driver. This can be used in the main module configuration or create a testing module which can be used only during testing.

<inherits name="org.senchalabs.gwt.gwtdriver.GwtDriver"/>

Finders

Window loginDialog = GwtWidget.find(Window.class, driver)
    .withHeading("log in").done();

loginDialog.find(Button.class).withText("Register").done().click();

Using findElement and GwtWidget.java

// Find the HorizontalLayoutContainer elements
WebElement hlcElement = driver.findElement(
    new FasterByChained(By.xpath(".//div/*"), new ByWidget(driver,
        com.sencha.gxt.widget.core.client.container.HorizontalLayoutContainer.class)));

// Find the VerticalLayoutContainer elements in HorizontalLayoutContainer
List<WebElement> vlcElements = hlcElement.findElements(
    new FasterByChained(By.xpath("//div"), new ByWidget(driver,
        com.sencha.gxt.widget.core.client.container.VerticalLayoutContainer.class)));

// Find the left widgets in the VerticalLayoutContainer element
WidgetContainer leftWidgets = new WidgetContainer(driver, vlcElements.get(0));
List<GwtWidget<?>> leftButtons = leftWidgets.findWidgets(By.xpath(".//div"));

// Find the button widget
Button lb = leftButtons.get(0).as(Button.class);

Interacting with Widgets

As each GwtWidget model has an internal reference to the WebElement it is based on, interacting with the widget is usually about as simple as interacting with that element. Typically, each GwtWidget should provide some basic methods for interaction, but inevitably there will be the need to provide extra functionality - you can invoke getElement() to get the root element in the widget.

Building your own models

If you've developed your own widgets, you will need to build your own widget models and finders based on the structure you expect your widgets to be used in and how you expect to need to search for them. The gxt-driver project includes a number of models and finders that can serve as a basic example of how to find and interact with widgets in a running application.

GXT 3.x