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.

Sencha Test 2.4.0


Introduction to Event Recorder

The event recorder is a key element of Sencha Test. It tracks user actions and creates meaningful code that indicates the following:

  • What kind of action a user performed - “tap”, “type” etc.
  • Where did the user perform the action - “button”, “form field” etc.
  • How is the target identified - id, component query, composite query, XPath

For a list supported browsers on each platform, please see Event Recorder Browser Support.


When a user performs an action like tapping a button or typing into a form field, the user's action is captured. Where the user has performed the actual operation is identified using the locator.

The Sencha Test event recorder offers three distinct strategies for getting component references; ID, Component Query, and XPath.


The ID of the element under test is captured. This could be a value dynamically generated by the Ext JS framework. This means that it may not be stable for long term test automation.

Component Query

Ext JS / ExtReact component query lets you identify exactly where a component resides in the hierarchy. The query can be helpful to identify the exact element using one of its properties such as title, class, etc.

Using the Event Recorder

Follow these steps to use the event recorder.

  1. Open a Jasmine test suite file

  2. Create a new test case. Jasmine test cases should be written inside of an it function, which resides within a describe function.

     describe('login form', function () {
         it('should deny access with wrong creds', function () {
             // Your test code goes here
  3. Before recording, ensure you have set the target application’s URL in the project settings screen. Without setting a valid URL, you won't be able to launch your application under test via the event recorder.

  4. Place the cursor inside of the it block and launch the event recorder by clicking the Event Recorder button.

    Event Recorder

  5. A window will be shown with browser options. If you're using the Sencha Test 2 WebDriver scenario option, you will be able to record using the embedded Google Chrome browser option out of the box. For this, you will need to have Google Chrome installed on the target machine.

    If you are running an In-Browser scenario option, you will be able to use any of the local browsers on your machine for recording.

    Browser Selection

  6. Once the browser is selected, the application is rendered in the browser. Wait for the recorder to be ready before you perform actions on the application. Look for the following screen before you start working on the application.

    Recorder is Ready

  7. Perform various operations on the application based on the purpose of your test case.

  8. The events are captured as the operations are performed. In Sencha Studio, a grid is displayed in the Event Recorder window. Check the value in the Target column. This could be an auto-generated id by the Ext JS or ExtReact frameworks.

    Click on one of the locators in the Target column, and you will be able to edit or select one of the other locators generated by the Event Recorder. Based on where the actions are performed, a component query may be generated. Select this option for more stable test execution.


  9. In the above screen, there is a grid with a Target column. This represents the target locators for identifying elements within the application. In an Ext JS and ExtReact application you will see multiple locator strategies such as ID, component query, etc. For any other web application, the ID or XPath will be captured by the Sencha Test event recorder.

  10. Once you have finished recording all of the steps from the test case, click on the "insert recording" button.

  11. The recorded scripts are stored under a ST API called It looks something similar to this:[
        { type: "tap", target: "treelistitem[text=\"Email\"]", x: 99, y: 44 },
        { type: "tap", target: "treelistitem[text=\"Profile\"]", x: 89, y: 41 },
        { type: "tap", target: "button[text=\"Follow\"]", x: 99, y: 33 }

    Inserted Code

  12. Finally, add any expect statements after the block.

Sencha Test 2.4.0