Info
Hierarchy
You can build Test Cases in any hierarchy you want to!
Reusing Test Cases
There are various ways to make your Test Cases more reusable.
First Steps Overview Keywords

Test structure

Useful terms:

1. Projects are containers for your Test Cases and Test Suites. They also contain information about your application under test (AUT), including how and where to start it.
   Projects are stored in a database, and can also be exported and imported in XML format.
2. Test Suites are the executable elements. Fill your Test Suites with the Test Cases you want to execute.
   Test Suites are bound to an AUT.
3. Test Jobs are collections of Test Suites. A Test Job can be used to test different instances of the same AUT, or different AUTs within one test run.
   Test Jobs are bound to an AUT via its ID.
4. Test Cases are the building blocks (keywords) for your tests. They can contain Test Steps and other Test Cases.
   Combine Test Cases to create larger, more complex Test Cases.
5. Test Steps are the smallest available units. Each Test Step contains three pieces of information:
   1. The component to be tested in the interface
   2. The action to execute on the component
   3. The data (or parameters) for the action
   You also enter a component name, which is your own name for this interface component. This name is joined to the real component name in the AUT later.
6. Most of the time, you will not be working with Test Steps, but with the library of unbound modules, which contains ready made Test Cases to reference in your tests. Each unbound module represents one Test Step to carry out a particular action. The library makes test creation easier by allowing you to drag and drop modules to create your Test Cases.