Glossary

This glossary provides terms and definitions for the [product name] software and products.

The following cross-references are used in this glossary:

See refers you from a nonpreferred term to the preferred term or from an abbreviation to the spelled-out form.
See also refers you to a related or contrasting term.

A

application node: In testing, an application that serves as a container to hold related test elements.
application stub: In testing, a program used as a placeholder to simulate the behavior of software components such as a procedure on a remote machine.
array variable: A representation of a changeable value for an element in an ordered collection or group of elements.

certificate store: The Windows name for a key repository.
compound test: A test asset type that is used to group tests into larger test flows. The tests in a compound test can all be of the same test type or of a different type.
conditional block: A compound statement that can run portions of a test depending on the value of a reference or field reference.

data correlation: A process by which the response received in a previous request is taken as the input data for the next request. See also dynamic data, substitution rule.
data pool substitution: The act of replacing a value in a recorded test with variable test data that is stored in a data pool.
dynamic data: In testing, data from a data pool, variables, or data correlation. See also data correlation.

equivalence class: A classification of values for which an object is expected to behave similarly.

functional report: A report that summarize the pass or fail verdicts for a test.

generated test: A test that is created automatically by recording the user actions.

hybrid app: See hybrid application.
hybrid application (hybrid app): A mobile device application that combines elements of web and native applications.

instrumentation: The process of including code in a program to monitor or enhance the operation of a system or component.
instrumented application: An application that is augmented with code so that it can capture and report data for testing.

managed application: An instrumented version of an application that has been added to a project in the test workbench.

native app: An app that is compiled into binary code for use on the mobile operating system on the device.

passive mode: In testing, a mode where the execution of a test is controlled remotely by a script or a batch file rather than a human.
polling interval: The frequency at which data is collected from the device resources such as CPU and memory.
project area: An area in the repository where information about one or more software projects is stored.

resource monitoring: The measurement of resource usage such as processor, physical memory, network traffic in and out, and battery of the mobile device and the application under test.
response time: The time that an application spends in processing a request.

segmented data pool: A data pool that is divided into a fixed number of rows that are assigned to each virtual user during a test.
silent mode: A method for installing or uninstalling a product component from the command line with no GUI display. When using silent mode, you specify the data required by the installation or uninstallation program directly on the command line or in a file (called an option file or response file).
stub: A component containing functionality for testing purposes. A stub is either a pure "dummy", just returning some predefined values, or it is "simulating" a more complex behavior.
substitution rule: A data correlation rule for which it is not necessary to manually correlate data for every test that is recorded for an application. See also data correlation.
synchronization policy: The rules that govern the calculation of response time for a native app, where synchronization is that state where a response is received and the app is waiting for a user action.

test asset: The information that is used to create, run, and evaluate tests. Test assets include plans, designs, test cases, test logs, and test reports.
test script: A collection of step-by-step instructions that realize a test, enabling its execution. Test scripts may take the form of either documented textual instructions that are executed manually or computer readable instructions that enable automated test execution.
test workbench: The user interface and integrated testing environment in tools such as HCL OneTest™ Studio.
think time: The time that a human takes to initiate a request after a response to a previous request has been displayed.

web app: See web application.
web application (web app): An application that is accessible by a web browser and that provides some function beyond static display of information, for instance by allowing the user to query a database. Common components of a web application include HTML pages, JSP pages, and servlets.
wrap: To go from the last row of a data pool or a segment thereof to the first. See also wrap mode.
wrap mode: A manner in which data is retrieved from a data pool by a virtual user during a test. Depending on whether a data pool is segmented, the data is fetched once per user or wrapped back to the first row when the last row is reached. See also wrap.