The format used to represent Test Cases in the Cyara Platform will be different to the one used in Quality Center. A mapping must be applied to the Cyara Test Case entity if you want to convert it to a form that can be stored and managed in Quality Center. This section will describe the mappings that are used.
Test Cases
In QC, the following database entities will be affected:
- TEST
- VC_TEST
Cyara Test Case Property | QC Entity | QC Field | QC Label |
---|---|---|---|
Description | TEST, VC_TEST | TS_DESCRIPTION | |
Phone Number | TEST, VC_TEST | Phone Number | |
Major Threshold Count | TEST, VC_TEST | Major Threshold Count | |
Minor Threshold Count | TEST, VC_TEST | Minor Threshold Count | |
Notes | TEST, VC_TEST | TS_DEV_COMMENTS | |
Alert Message | TEST, VC_TEST | Alert Message | |
Status | TEST, VC_TEST | TS_STATUS | |
Data Driven File | STEP_PARAMS | SP_PARAM_NAME
SP_PARAM_ACTUAL_VALUE |
Test Case Steps
In QC, the following database entities will be affected:
- STEP (where XX = ST)
- DESSTEPS (where XX = DS)
- VC_DESSTEPS (where XX = DS)
Cyara Test Step Attribute | QC Entity | QC Field | QC Label |
---|---|---|---|
Description | STEP, DESSTEPS, VC_DESSTEPS | XX_DESCRIPTION | |
IVR Prompt | STEP, DESSTEPS, VC_DESSTEPS | XX_EXPECTED | |
VQ | STEP, DESSTEPS, VC_DESSTEPS | VQ | |
Reply With | STEP, DESSTEPS, VC_DESSTEPS | Reply With | |
Reply Type | STEP, DESSTEPS, VC_DESSTEPS | Reply Type | |
Min Max Pause Time | STEP, DESSTEPS, VC_DESSTEPS | Min Max Pause Time | |
Major/Minor Conf/MOS | STEP, DESSTEPS, VC_DESSTEPS | Major/Minor Conf/MOS | |
PSST | STEP, DESSTEPS, VC_DESSTEPS | PSST | |
Minor/Major | STEP, DESSTEPS, VC_DESSTEPS | Minor/Major Threshold |
Data Driven Test Cases
Cyara Data Driven Test Cases appear as a single Test Case inside the Cyara Platform, but are run multiple times with different data inputs. Data Driven test inputs are defined as a file of comma separated values. The file contains a set of parameter values used for each test run.
Quality Center has a similar concept, but is implemented differently. Quality Center requires two Test Plans to represent a single Cyara Test Case. These are:
-
Template Test Plan
This is the Quality Center equivalent of the Steps within the Cyara Test Case, where you will see the parameter names used in the various text fields (For example, Expect to Hear, Reply With) of a Step. In Cyara, these parameters are declared within [ …], while in Quality Center they are declared within
<<<…>>>
or<<>>
(this latter representation hides the parameter name and when you click on the delimeter<<>>
, it displays the name).The template Test Plan name is the Test Case name with a ‘template’ post-fix.
-
Parameterized Test
Plan
This is the Quality Center equivalent of the ‘Data Driven’ sets within the Cyara Test Case. A row for each Test Case data driven set appears. Here, each row contains all the parameter names of the data driven set with its equivalent value. This means you will see as many rows in the Parameterized Test Plan as there are data driven sets within the Test Case.
The Parameterized Test Plan name is the Test Case name.
For example, the following screen shows Test Case Steps being
imported into Quality Center:
When imported, the two 'Test Plans' that QC generated for the above
Test Case are shown, as per the screen below:
The first one contains the various data driven iterations. The second one contains the data driven template.
- Click the data driven
iterations, and a screen as shown below appears:
- Click the data driven
template, and a screen as shown below appears:
The steps contain parameter placeholders that can be recognized by the
enclosing
<<>>
delimiters.
- Double-click the cell
under the
Reply with column name, then the
<<>>
delimiters display the actual Reply With token as shown:
Blocks
Blocks, for a Test Case, are not imported into Quality Center. Instead, each Test Case is flattened so the Blocks are replaced with the Test Steps they contain.
Comments
0 comments
Please sign in to leave a comment.