Creating more than one ExecutionRecord/Result using RQMExcelWordImporter-5.0.2 is not working
I'm using RQMExcelWordImporter-5.0.2 to create RQM artifacts from an excel with this structure by each row :
TestPlan
TestCase1 | TestExecutionRecord1 | TestExecutionResult1 | TestExecutionRecord2| TestExecutionResult2 | TCER3|TCERR3
I can create TestPlan, TestCase1, TestExecutionRecord1 and TestExecutionResult1. In order to do this I'm using (what I'm presenting now is a simplification to explain main situation, I have other fields related with other columns) :
executionworkitem.XLSArtifactID="executionworkitem_" & B (where B is Column where TestCAse Description is)
executionworkitem.ID= B
Also consequently I'm creating relationships :
executionworkitem.testcase=Link(B)
executionresult.testcase=Link(B)
Everything works fine to create TestExecutionRecord1 & TestExecutionResult1. Nevertheless for 2 & 3 there is no way to create new entries. I have done a lot of test trying to describe a new artifact for 2 and 3. Also I have tried to add a new TCER after testPlan,testcase creation from another excel (in this case I used ids to refer rqm artifacts using /urn:com.ibm.rqm: NOTATION)
My questions :
1.- It is possible to create more than one TCER from an excel using RQMExcelWordImporter??
What is the notation/syntaxis to do this?
Where I can find an example to do it? (All examples just create one TCER)
2-. Is there another way to do this?
|
2 answers
Hi Renzo,
To create more than 1 TCER for a testcase you need to follow a simple rule. Each TCER should have diff test env values or diff testplan, you cannot create multiple TCERs for a TestCase with all the details same except name. |
Reshma :
Is not working...
I created 2 envs. I'm trying to create 2 TCERS in a same load process.. seems is not possible use elements twice in the cfg. Example : "Element XLSArtifactID was added"
====
//TCER 1
executionworkitem.XLSWorksheetID="Script"
executionworkitem.XLSStartRow=3
executionworkitem.XLSArtifactID="executionworkitem_" & B
executionworkitem.dc:title=B
executionworkitem.dc:starttime=O
executionworkitem.dc:description=G
executionworkitem.configuration=Link(BY)
executionworkitem.testphase=Link(BZ)
executionworkitem.testplan=Link(property("name"))
executionworkitem.testcase=Link(B)
//TCER2
executionworkitem.XLSWorksheetID="Script"
executionworkitem.XLSStartRow=3
executionworkitem.XLSArtifactID="executionworkitem_" & B
executionworkitem.dc:title=B
executionworkitem.dc:starttime=O
executionworkitem.dc:description=G
executionworkitem.configuration=Link(BW) ---> Other env
executionworkitem.testphase=Link(BZ)
executionworkitem.testplan=Link(property("name"))
executionworkitem.testcase=Link(B)
====
27/10/2015 11:22:34 a. m.: ERROR: <Unknown Caller Context>: Config File Line: 85 Ya se ha agregado el elemento. Clave en el diccionario: 'XLSArtifactID' Clave agregada: 'XLSArtifactID'
27/10/2015 11:22:34 a. m.: ERROR: <Unknown Caller Context>: Config File Line: 87 Ya se ha agregado el elemento. Clave en el diccionario: 'dc:title' Clave agregada: 'dc:title'
27/10/2015 11:22:34 a. m.: ERROR: <Unknown Caller Context>: Config File Line: 88 Ya se ha agregado el elemento. Clave en el diccionario: 'dc:starttime' Clave agregada: 'dc:starttime'
27/10/2015 11:22:34 a. m.: ERROR: <Unknown Caller Context>: Config File Line: 89 Ya se ha agregado el elemento. Clave en el diccionario: 'dc:description' Clave agregada: 'dc:description'
27/10/2015 11:22:34 a. m.: ERROR: <Unknown Caller Context>: Config File Line: 90 Ya se ha agregado el elemento. Clave en el diccionario: 'configuration' Clave agregada: 'configuration'
27/10/2015 11:22:34 a. m.: ERROR: <Unknown Caller Context>: Config File Line: 102 Ya se ha agregado el elemento. Clave en el diccionario: 'testplan' Clave agregada: 'testplan'
27/10/2015 11:22:34 a. m.: ERROR: <Unknown Caller Context>: Config File Line: 103 Ya se ha agregado el elemento. Clave en el diccionario: 'testcase' Clave agregada: 'testcase'
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.