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.

Sencha Test 2.4.0


top

Introduction to Jira Integration

Sencha Test 2.1 brings expanded end-to-end automation support, from kicking off runs using a CI tool, to logging bugs in a defect tracking tool.

The ALM integration is the first step towards achieving an automated continuous testing strategy. In Sencha Test, users leveraging Jira as a defect management tool can take advantage of the integration.

With this integration:

  1. Users can review failed tests from the results published in archive server

  2. Ignore false negatives

  3. Publish verified bugs to Jira along with important information about the test, including assertions and screenshots

Important Notes

Integration with Jira utilizes Jira's REST API. Most instances of Jira have a limit on the number of unsuccessful login attempts that are allowed via the API before the user must login directly via the browser (this is based on administrative policy - see this document for more information). If the provided credentials are correct but login is unsuccessful, the user will have to first log in using a browser, and then attempt authentication again within Sencha Test.

Requirements

A local Archive Server and/or Remote Archive Server is required.

ALM Integration with Sencha Test Studio

Configuration of Jira integration is performed in the Sencha Test Studio preferences, within the Integrations tab.

Issues from test runs are created in the specified Jira instance from the Review Manager, available when displaying the Runs tab of Sencha Test Studio, where runs that are managed with an Archive Server are displayed.

Connect to Jira (One-time setup)

  1. Navigate to Preferences in Sencha Studio, and select the Integrations tab

  2. Initially, the integration status will show as '(disconnected)'

    Jira Disconnected

  3. Enter your information in the form

  4. Once the required information has been entered, Sencha Test will validate your credentials and allow you to select a default Jira project to receive issues created by Sencha Test.

Running Tests with an Archive Server

In order to save the test results to the local archive server, select the "Run + Save" option.

Review Manager

There are many reasons for tests to fail. Not all of them may warrant a bug though.

The review screen will present all the failed tests along with reasons for failure and screenshots (when available). Review the failed tests and publish failures that can be classified as defects.

  1. After results have been saved to the Archive Server, click on the Test Results tab in Sencha Studio and view the results by selecting the test run from the tree.

    Review test run results

  2. The test results are presented along with a "Review Test Run" button at the top of the screen. Click the Review Test Run button to start reviewing which issues you would like to push to Jira.

    Publish to Jira

  3. Click on a checkbox next to a failed test run and verify the details on the right hand side

  4. If a selected failed test run is not a bug check the "Ignored" checkbox

  5. Ensure all valid bugs are selected and click the "Send Failures" button

Fetch latest Jira status of a bug

This feature will help users to check for the current status of a bug before reviewing all the failed tests in the latest test run.

  1. Navigate to the review manager for the latest test run

  2. Click on the "Refresh Statuses" button and this will fetch the latest status of all the bugs on that test run.

Sencha Test 2.4.0