命令行工具CLI和归档服务器
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.
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.
Public classes and class members are available for use by any other class or application code and may be relied upon as a stable and persistent within major product versions. Public classes and members may safely be extended via a subclass.
Protected class members are stable public members intended to be used by the
owning class or its subclasses. Protected members may safely be extended via a subclass.
Private classes and class members are used internally by the framework and are not intended to be used by application developers. Private classes and members may change or be omitted from the framework at any time without notice and should not be relied upon in application logic.
static label next to the
method name. *See Static below.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).
Let's look at each part of the member row:
lookupComponent in this example)( item ) in this example)Ext.Component in this case). This may be omitted for methods that do not
return anything other than undefined or may display as multiple possible values
separated by a forward slash / signifying that what is returned may depend on the
results of the method call (i.e. a method may return a Component if a get method calls is
successful or false if unsuccessful which would be displayed as
Ext.Component/Boolean).PROTECTED in
this example - see the Flags section below)Ext.container.Container in this example). The source
class will be displayed as a blue link if the member originates from the current class
and gray if it is inherited from an ancestor or mixed-in class.view source in the example)item : Object in the example).undefined a "Returns" section
will note the type of class or object returned and a description (Ext.Component in the
example)Available since 3.4.0 - not pictured in
the example) just after the member descriptionDefaults to: false)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.
classInstance.method1().method2().etc();false is returned from
an event handler- 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
- 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
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.
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.
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.
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 and inheritance. This is done using the checkboxes at the top of
the page. Note that filtering out private members also filters the API class
navigation tree.
Clicking on an empty search field will show your last 10 searches for quick navigation.
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:
Ext.button.Button class has an alternate class name of Ext.Button). Alternate class
names are commonly maintained for backward compatibility.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.
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:
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.
In order to provide integration with continuous integration (CI) servers like Jenkins and Teamcity, Sencha Test allows you to execute tests for an existing scenario from the command-line. The command-line tool doesn't support launching of local browsers, which means a browser farm and browser pool must be configured for the target scenario.
Let's walk through executing a test via CLI.
The basic command-line syntax for executing a test from the command line is as follows:
stc run -o output -p pool -s scenario
Here are the optional flags that may be passed along via your command line execution:
-o <output> - Output format. Supported values are text, teamcity and junit
-p <pool> - Name of the pool from whence tests will be executed. This must be a pool associated with a browser farm
-s <scenario> - Path to the scenario to be executed. If unspecified, defaults to the current directory.
In the following example to be run from a Windows command line, we are executing tests for:
tests\unit_tests My WebDriver Pool Providing output in TeamCity format
stc run -o teamcity -p "My WebDriver Pool" -s tests\unit_tests
To perform image comparisons from screenshots, Sencha Test will use an existing run as the reference (baseline) against which each image will be compared. If a baseline for comparison is not present, all comparisons will pass, and the resulting archive directory can then be specified as the baseline for future comparisons.
To use a specific result archive as baseline, it has to be copied or renamed to ${workspace.dir}/reports/baseline. Alternatively,
the -b switch can be used to specify any arbitrary result archive directory.
-b <baseline> - Path to the result archive directory to be used as baseline for image comparisons
By default, Sencha Studio will assign a dynamically generated build number to each test execution. To specify the build
number for a given test run, the -n switch can be used.
-n <build_number> - Build number for the test execution
By specifying the baseline directory and the build number, it's possible to control all the directory and file names associated with the test execution. This way, one can easily archive test results and fetch arbitrary baselines in a CI system.
In order to execute tests in a cloud-based browser farm such as SauceLabs or BrowserStack, you can specify credentials, callback addresses while controlling the automatic launch of the provider's tunnel. Here are the options that may be applied:
-u <username> - Username for the browser farm
-k <key> - Access key for the browser farm
--notunnel - If specified, disables the automatic launch and teardown of the tunnel to the specified cloud provider. When
this switch is used, a tunnel for the specified username must be already running, either in the local machine or in a
dedicated host in the same network.
Note: The auto-connecting tunnel feature will not be available in the early access or beta releases. All tunnels will need to be manually created until auto-connection is available.
-c <callback_address> - Callback address - host or IP by which the farm browsers can dial back to Sencha Test's proxy.
If unspecified, defaults to localhost. This switch is particularly useful when a dedicated tunnel is being used. In such
case, it's likely to be the local machine's LAN ip address.
In the following example to be run from a Linux command line, we are executing tests for:
Tests found within tests\unit-tests
In the pool named SauceLabs pool
Providing output in Jenkins format
Using the credentials username:xxxxx-xxxx-xxxx-xxxx-xxxxx will be used
A SauceConnect tunnel will not be launched automatically. This means the user is responsible for starting one manually.
All browsers will attempt to connect to http://192.168.1.42
Example:
stc run -o junit -p "SauceLabs pool" -s tests\unit_tests -u user -k *x-x-x-x-x* --notunnel -c *192.168.1.42*
Sencha Test provides a component called "result archive server". This is the area in which test results can be stored for later review via the Sencha Test Studio GUI.
To set up an archive server, a configuration file called storage.json has to be created. This file must contain one
or more storage area definitions.
A storage area is defined as a property whose name is the key that users need to know in order to store results. The value is an object containing the physical path where its archives will be stored relative to the server root directory.
Here is a sample storage area.
{
"my_secret_key": {
"path": "/mystoragearea"
}
}
Note: Users must know the key my_secret_key in order to store archives under /mystoragearea on the
designated server.
These paths may contain multiple directory levels. These paths don't hold any special meaning. They can be reviewed by the server administrator in order to organize the test results archives and/or provide isolation across teams and projects. The keys are free-format strings.
In the following example, storage areas are separated by team. Each team, developers and qa in this case, need to know their key in order to store results in their respective storage areas.
{
"889jwx093jr8wuwer": {
"path": "/developers"
},
"sccmnn840394843": {
"path": "/qa"
}
}
In the next example, teams have isolated storage areas for each of their projects.
{
"879fnas9d8jf70sd": {
"path": "/TeamA/project1"
},
"mx348r343mr34cj": {
"path": "/TeamA/project2"
},
"sdnaaa090ilss": {
"path": "/TeamB/project1"
}
}
To start the result archive server, create a storage.json file in a dedicated directory and from there, run the
following from your CLI:
stc server
You should then see a success message:
Archive server listening on port 1903
Here's an example of how you'd set up your Archive Server on a machine:
mkdir archiveserver
cd archiveserver
vim storage.json #configure storage areas - see examples above
stc server
In order to send the result archive to a configured archive result server, you may use the following switches with
stc run.
-S <server_address> - Archive server address. If the archive result server host machine IP address is 192.168.1.42, for
instance, the value will be http://192.168.1.42:1903 (including the port number).
-K <key> - Key to the storage area. To store results in /TeamA/project2 (example above), the value will
be mx348r343mr34cj.
In the following example, we are:
tests\unit_teststeamcityMy WebDriver Pool192.168.1.42:1903 with port 1903mx348r343mr34cjExample:
stc run -o teamcity -p "My WebDriver Pool" -s tests\unit_tests -S http://192.168.1.42:1903 -K mx348r343mr34cj
Outputs similar to the ones below are expected after a successful result storage on the server:
Uploading archive to http://localhost:1903
Server response: 200 - Archive received
user:~$
Client: successfully uploaded test result archive
Receiving archive 28ea1080-a2a5-11e5-ac7d-51ab7d509196.zip
Archive 28ea1080-a2a5-11e5-ac7d-51ab7d509196.zip extracted to /home/user/archiveserver/TeamA/project2/foo/orion/28ea1080-a2a5-11e5-ac7d-51ab7d509196
Server: successfully received test result archive
A single test project will often have multiple scenarios. In these cases, you may want to run multiple scenarios as part of a single "build" in your CI system. This allows you to see all of the Scenario results as a single results set in Sencha Studio.
As an example, you may have Scenario A and Scenario B and you want to run both of these whenever code is merged.
Once all of your Scenarios are complete, the Archive Server will merge the results from Scenario A and B and Sencha Studio can then display the aggregated results as one logical build or test run number.
Sencha Test 1.0.3 | Terms of Use