A test session contains the overall test definition: the test cases that will be executed, the duration of the test, and the sequence of steps the session will follow during execution. You should have a basic understanding of the concepts covered by this topic before attempting to configure a test session.
A number of tests can be executed during the course of a test session, and each test is defined by a test case. You can create a new test case from a template in the Basic Test Case Library or add a test case to the session was previously saved to another section of the Test Case Library. A test case template is provisioned with default values for most of its settings (parameters). As you define each test case, you configure its parameters for your test environment and for the type of test that you want to perform in the test session. Test cases can be used in two modes, linked or local, and you should understand the difference between these modes before you continue.
The minimum requirement for an executable test session is that it contains one test case, but you can use optional features to define a test session that will execute a number of tests in a certain order (Automation Control) and define a duration for the test. These options can be used together or independently: you can define a test session that repeats a set of actions for a number of iterations, or you can define a test session that performs one or more tests for a specified duration.
In general, configuring a test session consists of the following steps:
After the test session has been configured and saved, you can close the session or execute the test.