Object Types

Information about the test is managed in a database and displayed in PAconfigurator. The structure of the database allows a hierarchical organization of all objects. The following object types are defined.

Database—Represents the entire database and therefore exists only once per database. All objects (configurations) are located below the database. You can create only certain types of folders under the database.

DSOs—Overview of all imported DSO archives.

Components—Overview of all imported test components.

Test —Contains all the information needed to solve a test task. A test can contain groups and group folders. It is also possible to add links to groups or group folders to a test. A test folder cannot contain several tests with the same name.

Test folder—Provides structure for the tests. Test folders can contain test folders or individual tests.

Workspace folder —Provides structure for global workspaces or workspaces within a test.

Groups, group types—For the definition of the test, different groups are composed graphically. They are located in tests or group folders. These groups are distinguished by their group type. Input variables of the test are defined, for example, in an Input variables group type.

Group folder —Provides structure for groups. Group folders include further subordinate group folders, individual groups or links to groups or folders. Group folders directly under the database serve as a library for tests.

Test component—Encapsulates self-contained functionality and adds functionality to a test. You can only create a test component in a test component folder.

Test component folder —Structures global test components or the test components within a test. It only can contain other test component folders or test components.

RLO folder (reloadable objects) —Collect and structure groups that you can reload at test run time. You can only generate these objects from the test context.

RLO library elements—Contains a complete set of reloadable components. Unlike RLO folders, RLO library items are always generated out as a whole, not as individual objects.

Links—Configures content only once for future use.