Test Projects |
A test project corresponds to the Natural application you want to test. It consists of one or more test cases. |
Defining Hosts |
The host containing the application you want to test. |
Session View |
The Session View is especially useful when working with screens or test cases, either offline (replay file) or online. |
Screens |
A single Natural Screen Tester screen represents a corresponding screen in the host. A Natural Screen Tester screen is usually
defined using unique text identifiers from the host screen, but it is also possible to use other identifiers such as the position
of the cursor when the screen is loaded or field attributes (Protected, Intensified or Hidden).
|
Screen Groups |
A screen group binds several screens that share common visual or logical attributes. The relationship between screen groups
to screens is many-to-many: a screen group can include many screens, and a screen may be included in many groups.
|
Working with Entities |
Working with Natural Screen Tester entities. |
Procedures |
A Natural Screen Tester procedure is a well-defined encapsulation of a complete process, and contains process input arguments,
process output arguments and the process definition itself.
|
Test Project Map |
The Test Project Map view displays thumbnails of the screens which the user navigated through when working with test project. |
Data Structure |
A Data Structure is an object that is characterized by attributes. Once defined, the Data Structure entity can be used as
an input or output variable in Procedures or as an attribute of a Data Structure.
|
Database Connection |
A database connection is an entity that is used for direct database access in a flow procedure. |
Connection Pools |
A connection pool enables you to immediately get a host connection that is ready in a specific screen, the "initial screen".
This saves the time of establishing the connection with the host and navigating to the relevant screen.
|
Connection Information Sets |
A connection information set supplies a pool of possible connection parameters required for the initial connection to the
host (such as the device type or host address) and for the execution of the connection pool initialization path when it exists
(such as the required user name and password).
|
Session Data |
Session data is an entity used to save session context information. Each test project has a single session data entity, located
in the repository folder.
|
Managing Test Data |
In Natural Screen Tester, a JSON file (JavaScript Object Notation) is generated by the Generate Unit Test wizard from the
test project. It contains inputs and assertions for the unit test as attribute-value pairs. You can copy a generated JSON
file and change the inputs and assertions. The unit test is then run multiple times, once for each JSON file.
|
Working with JSON Files |
In Natural Screen Tester, a JSON file (JavaScript Object Notation) is generated by the Generate Unit Test wizard from the
test project. It contains inputs and assertions for the unit test as attribute-value pairs. You can copy a generated JSON
file and change the inputs and assertions. The unit test is then run multiple times, once for each JSON file.
|
Batch Automation Utilities |
|