This document is specifically for inline-QA Test Session. Please refer to the Test Session User's Guide document for how to use the Test Session Editor application.
1.0 CREATING A NEW TEST SESSION
When you create a new test session object, you need to set the Inline-QA to True.
The Inline-QA identifies this object is for when then inline-QA selection is set to True. When this is set to True, the Policy area is disabled as you can only use Standard policy. When this is set to True, the program set the enableInLineQA test session attribute to have the value of true.
When done with entering the fields, click the OK button and the newly created test session is available in Guru. The attributes paragraph is filled in with the necessary information to identify the test session when a new test session object is created. After creating a test session object, the user can then define which testplans to use.
2.0 ATTRIBUTES
After the new test session is created or after loading an existing test session object, we can start editing the test session object. First, lets make sure that the enableInLineQA attribute is set correctly. Go to the Attributes page.
The attributes display some information regarding the Test Session object. The test session attributes are displayed on the top in the Attributes page of the Test Session Editor window.
We are looking for a specific attribute named enableInLineQA. This attribute must have a value of true.
If the enableInLineQA does not have the value of true, you need to modify this attribute by selecting this attribute and either double click it or RMB and select the Edit menu.
If the test session object is missing the enableInLineQA attribute, you can add by RMB and select the Add menu.
Within the add attribute window, select the enableInLineQA for the Name and select true for the Value.
Click the OK button to apply the changes and the attribute will be displayed in the attributes area.
2.1 VIEWS
The Views area lists which worksheet(s) to be displayed. Refer to the Test Session User's Guide Section 3.5.2.2 Views for details of editing the views area.
3.0 TESTPLAN
Select the testplan page to add or edit the testplans being used in this test session object.
3.1 TESTPLAN GROUP
For inline-QA, we must have two testplan groups. testplan1 and testplan2, defined. They can both be the same testplan object or they can be different testplan objects. Refer to the Test Session User's Guide Section 3.5.3 Testplan for details of adding and editing testplans.
3.2 TESTPLAN ATTRIBUTES
The testplan attributes must have type attribute defined for inline-QA. The first testplan. testplan1, has a type attribute of primary and the second one, testplan2, is inlineQA. The following are the testplan attributes for inline-QA, in addition to the general testplan attributes defined in Section 3.5.3.2 Testplan Attributes of the Test Session User's Guide.
qaRate -- the first testplan is always 100, you can change this value for the second testplan
type -- the first testplan has a type of primary, the second testplan has a type of inlineQA
The testplan also needs to refer to refer to a datalog. For inline-QA, we need to create two datalog groups (see Section 4.0 Datalog). The second testplan (with type of inlineQA) must refer to datalog group which has a type of RITdb. The first testplan can refer to datalog which can have either STDF or RITdb. We suggest both datalog have RITdb format.
To add or edit an attribute to a testplan, RMB in the testplan attribute area and select the Add or Edit menu.
In summary, the following are examples of two testplans' attributes for inline-QA:
testplan1
datalog -- datalog1
title -- title of the testplan
qaRate -- 100
type -- primary
testplan2
datalog -- datalog2 (must have RITdb as its format)
title -- title of the testplan
qaRate -- 10 (any number less than 100)
type -- inlineQA
4.0 DATALOG
Select the datalog page.
The inline-QA requires two datalog groups to be defined. datalog1 and datalog2.
Click the Add button to add a datalog definition, or if you already have one datalog group defined, you can click the Copy button to copy the definition.
The first datalog can have the format of RITdb or STDF. The second datalog must have format of RITdb.
Please refer to Section 3.5.7 Datalog of the Test Session User's Guide for details of adding/editing the datalog for the test session object.