Home
Reference Guide
This guide describes conceptual information about data design environment components when you want to use the data fabrication feature in HCL OneTest™ Server.
Schema design
A schema is a graphical data dictionary that contains metadata definitions of the structure of a document to generate test data. Schema provides visual cues for understanding the structure and complete definition of an object.
Functions and expressions
Logical functions
NOT

Reference Guide
This guide describes conceptual information about data design environment components when you want to use the data fabrication feature in HCL OneTest™ Server.
- Files
  You add a file to a project to use it as input in the project. You can upload a file from your local file system to a project from the Files tab to generate test data. Alternatively, you can upload it when you define an action.
- Connections
  A connection defines the properties that are required to connect to an external resource. An action uses a connection to provide source data to a project or write data from a source to a target. Multiple actions can use the same connection. You can define both connections and actions at the project level.
- Schema design
  A schema is a graphical data dictionary that contains metadata definitions of the structure of a document to generate test data. Schema provides visual cues for understanding the structure and complete definition of an object.
  - Introduction to schema design
    Use the Schemas tab to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.
  - Type properties
    The properties of a type define the characteristics of the data objects of that type.
  - Item restrictions
    Item restrictions are an optional feature you can use to specify valid or invalid data objects for an item type. Item restrictions are grouped into three categories: Value, Character, and Range.
  - Components
  - Partitioning
  - Type inheritance
  - Schema analyzer
  - Distinguishable objects
  - Functions and expressions

NOT

Use the NOT function to test a condition and have it return the inverse of its "true" or "false" result. For example, you want the function to return "true" if the condition results in "false".

Syntax:: NOT (single-condition-expression)
Meaning:: NOT (condition_to_evaluate)
Returns:: "True" or "false"

NOT returns "true" if the condition evaluates to "false" and returns "false" if the condition evaluates to "true".

Examples

NOT (Qty:.:InputFile = 0)
This example returns "false" if the Qty equals 0 (the condition is true) and returns "true" if Qty does not equal 0 (the condition is false).
IF (NOT (PRESENT (StartDate)), "Unknown", "none")
This example returns "unknown" if StartDate is not present and returns "none" if StartDate is present.

Another way to test that an object is not present is to use the ABSENT function.