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

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.


item :  Object

The config object being added.


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.



Using Sencha WebTestIt with existing projects

In many scenarios, the automated tests are part of the source code of the website or application you are developing. Those projects are created by an integrated development environment (IDE), like IntelliJ IDEA or Visual Studio.

You can use Sencha WebTestIt to open existing projects from other IDEs and edit the test cases in it, as long as you follow a few basic rules.


Editing tests in existing projects only works if your test environment uses one of the supported test frameworks >If you are using different frameworks for test execution, Sencha WebTestIt will not be able to integrate.

To get started, open the root folder of your development project in Sencha WebTestIt. In the following dialog, you need to provide some information to create a new Sencha WebTestIt configuration file. This mainly concerns a project name and the language to be used.

After adding a configuration file, you can use the Project tab to browse your files. You can add new Page Objects and Test files as you would in an empty project.

How to make existing files work with Sencha WebTestIt

Sencha WebTestIt relies on contextual comments in your source files to identify them as core objects. Core objects are test files or Page Object files and cause the Sencha WebTestItt UI to adapt.

Existing Page Object files in your project need to be modified in order to use functionality like Drag&Drop.

To make a Page Object file detectable as such, you need to add the following comment in the first line of the file: // Sencha WebTestItt Page Object File in the Project tab. The file changes its icon and look like you created it in Sencha WebTestItt.

The editor displays the special comment in a different color, the user interface enabled you to create selectors without the need of writing code.

In test files you need to specify them by applying the following comment in the first line of the file: // Sencha WebTestIt Test File.

If you click a test file modified like this, Sencha WebTestIt opens the Execution tab and enable you to directly run it on configured endpoints.

Adding new elements

You can add new Page Object files and test files to your existing project as you would in your Sencha WebTestItt Project by following these steps:

  1. Go to the Project tab and select the folder where you want to create your new files (or create a new one).
  2. Right-click the folder and select New > Page Object file to add a new Page Object, or New > Test file to add a new test.
  3. Sencha WebTestItt automatically scans your project infrastructure for tests and execute them if you click Run all test files in the Executetab.