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
Partitioning types
Partitioning an item type using restrictions
Example of using restrictions

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

Example of using restrictions

You have new data that needs to be entered into the Type Designer. Each new record contains the name of the employee and his or her department.

The Employee List schema illustrates components of Record.

The following is the new data containing the name of the employee and the department.

Steven Barlow,Doc

Heather Proust,Qa

Mary Whiting,Doc

Genie Elks,Sup

Francine Maxwell,Dev

Mark Brown,Sup

Daryl Schwartz,Acc

Harry O'Brian,Sal

Ellen Randolph,Dev

Paula Keller,Qa

Define the values of Department as a character text item.

Define the example data as valid restrictions (enter in the Include column) of Department:

If the departments are located in different offices, you can divide the data into separate files; one file per office. To do this, map the data from the main office to one file, the data from the development office to one file, and the data from the support office to another file. Then create subtypes of Department: MainOffice, DevelopmentOffice, and SupportOffice and partition Department. When you partition Department and create subtypes, you are saying that a given department data object belongs to only one of the subtypes based on its value.

The subtypes of Department inherit the restrictions of Department. Now allocate restrictions among subtypes. To do this, delete the restrictions from the subtype that do not apply to that particular office. For example, the MainOffice item has only the departments in that office, DevelopmentOffice item has only the departments in that office, and the SupportOffice item has only the departments in that office.