| 6.6. Test Segments | ||
|---|---|---|
|
Chapter 6. Define |  |
| 6.6. Test Segments | ||
|---|---|---|
|
|
Chapter 6. Define | |
Only available in Klaros-Testmanagement Enterprise Edition
A test segment defines and encapsulates a sequence of test steps. In test cases, these test segments can be shown as test steps. The content of a test segment is edited centrally here and the changes are automatically applied in the test cases. This chapter shows how test segments are created and edited.
The overview page displays all existing test segments in the selected project in a table. New test segments are created here.
The table shows the following values:
|
ID |
Assigned automatically. |
|
Additional Information |
A tooltip appears when the cursor is placed over the icon shown here. |
|
Revision |
The revision of the test segment. |
|
Name |
The name of the test segment. |
|
Steps |
The number of defined test steps. |
|
Test Cases |
The number of test cases in which this test segment occurs. |
The Name entry can be edited directly in the table rows by clicking in the corresponding field.
By clicking on the button a a new empty table row will appear. Now, a Name can be defined.
With the new test segment is created and saved. The ID of the test segment (SEG00001) is automatically assigned. Clicking on the ID SEG00001 takes you to the detail page of the test segment.
With several table rows can be created and edited at the same time. Only when clicking on the data is stored in the database.
With all changes are undone.
![[Note]](images/note.png) |
Red IDs |
|---|---|
|
All rows with red IDs have been changed and are not yet saved! |
The following actions can be performed in the action column:
If a test segment has been deleted, it is initially marked with a deletion marker and is only visible to administrators. For deleted test segments, the following actions are available instead of Delete:
Certain actions can also be applied to several test segments simultaneously. To do this, select the test segments to which the action is to be applied in the leftmost column.
The following bulk actions are supported for System under Test:
Bulk actions are described in detail in Section 5.2.3.1.5, “Bulk Actions”
The following operations can be performed in the line above the table on the right:
All operations are described in detail in Section 5.2.3.1, “Overview Page”.
Each test segment has its own detail page with several additional tabs. Clicking on the ID of the relevant test segment or on the icon on the right in the action column takes you to the tab that was selected last. When called for the first time, this is the Properties tab.
The following tabs are available: Properties, User Defined, Steps, Attachments, Revisions, Test Cases, and Changes.
On the detail pages, there are additional icons in the top right corner of the header. The following actions can be performed here:
|
Open print view |
A print-ready view of the test segment can be created here. With a click on the icon this opens in a new browser tab. Print views are described in detail in Section 5.2.3.2.1, “Print Pages”. |
|
Create Bookmarks |
Each individual detail page can also be reached directly via a hyperlink. By clicking on the icon this link is copied to the clipboard. The creation of bookmarks is described in detail in Section 5.2.3.2.2, “Bookmarks”. |
|
Browse |
Use the green arrows at the very top right to switch between the test segments present on the previous page. |
In this view ( Figure 6.37). the following attributes of the test segment can be displayed and can be edited:
|
ID |
Assigned automatically. |
|
Name |
The name of the test segment. |
|
Description |
The textual description of the test segment. |
|
Precondition |
The precondition of the test segment. |
|
Expected Result |
The expected result of the test segment. |
|
Postcondition |
The postcondition of the test segment. |
|
Note |
An optional note. |
|
Editor Settings |
|---|---|
|
Under Define --> Project --> Properties you can set whether the editor displays only text or HTML. With the HTML setting, a bar with formatting options appears when you click in the text field. |
Clicking the button saves the selected changes to the database, discards the changes.
You can create your own fields to meet individual requirements. For further information please refer to Section 5.2.3.2.4, “User Defined Properties”.
The test steps contain the following information:
|
Actions |
The description of the action to take, e.g. Enter name and password, and click the Login button. |
|
Expected Result |
The (visible) behavior of the system predicted while carrying out the test step e.g.
The user receives a message that the login succeeded.
|
|
Precondition |
The Condition that must be fulfilled before the execution of the test step,
e.g. The user is not yet logged in. |
|
Postcondition |
The environmental and state conditions that must be fulfilled after the execution of the test case,
e.g. The user is authenticated and has access to the system..
|
You can add any files as attachments to a test segment. For more information, see Section 5.2.3.2.6, “Attachments”.
Test segments may exist in different revisions. For more information, see Section 5.2.3.2.5, “Revisions”.
The page displays a list of test cases assigned to the selected system under test.
The following values are displayed in the table:
|
ID |
Assigned automatically. |
|
Revision |
The revision of the test segment. |
|
Name |
The name of the test segment. |
|
Traceability |
A reference to the corresponding requirement, use case or work package. |
|
State |
The state of the test case. Possible values are Locked, Approved, Draft and Skip. |
|
Steps |
The number of test steps. |
For more information see Section 6.7, “Test Cases”.
The tab Changes shows the change history of this test segment.
For a detailed description of the Changes view, see Section 5.2.3.2.8, “Change History”.
|
|
 |
|
| 6.5. Systems under Test |  |
6.7. Test Cases |
