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.
Partitioning
Determining when to partition
Partitioning for convenience

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
    - Determining when to partition
    - Partitioning types
  - Type inheritance
  - Schema analyzer
  - Distinguishable objects
  - Functions and expressions

Partitioning for convenience

You might decide to use partitioning in your schema to build additional logic into the definition of your data. You may also use partitioning to simplify the rules.

The following is an example of partitioning to simplify rules. The example compares the differences between rules needed with and without partitioning. In the rule without partitioning, you would specify a condition for each state abbreviation in each region. This could make your rules long, difficult to read, and difficult to maintain. The rule with partitioning is more concise, self-documenting, and easier to maintain.

Rule without partitioning:

=IF(ShipToCode Field:.:Input="NY"|
    ShipToCode Field:.:Input="NJ"|
    ShipToCode Field:.:Input="PA",
    F_MapEast (Record:Input), NONE)

Rule with partitioning:

=F_MapEast (EXTRACT (Record:Input,
PARTITION (ShipToCode Field:.:Input, East)))