It's all about the answers!

Ask a question

RQM Excel importer error, Error sending to server ** of type executionworkitem


Jeffrey Behnke (2711) | asked Dec 12 '16, 10:21 a.m.

We are experiencing an issue when using the RQM excel importer to import test cases and results into RQM. Our excel file consists of the test case, execution record and result on one line of the excel. A second test case, execution record and result exist on the next line. When we run the import, the import finishes, but we are receiving the following error Error sending to server tcerid20006 of type executionworkitem

When reviewing the test cases in RQM, both results are getting placed on one test cases, which is not the expected and desired outcome. One line on the excel comprises all of the details for test case A and the next line for test case B.

What else do we need to include on our config file to insure that one line on the excel is processed completely, before the next line?

Details of the import:

Sending testcase 0 named 20007...

Sending testcase 1 named 20006...

Sending executionworkitem 2 named tcerid20007...

Sending executionworkitem 3 named tcerid20006...

Error sending to server tcerid20006 of type executionworkitem

 

Sending executionresult 4 named resultid20006_01...

Sending executionresult 5 named resultid20007_01...

 

Exporting completed with 1 failures!

Details of config file:

testcase.customAttributes identifier="QC_TC_ID".name="External Test Case ID".type="Integer".value=A

 

// static test case definition

testcase.XLSStartRow=2

testcase.XLSArtifactID=A

testcase.dc:title=B

testcase.dc:description=B

 

// static configured testcase definition with link to testcase

executionworkitem.XLSStartRow=2

executionworkitem.XLSArtifactID=C

executionworkitem.XLSLink=testcase

executionworkitem.dc:title=D

executionworkitem.dc:description=D

 

// result definition starting at line 2 in the spreadsheet

executionresult.XLSStartRow=2

executionresult.XLSArtifactID=E

executionresult.XLSLink=executionworkitem

executionresult.dc:title=F

executionresult.er:details=F

executionresult.jzalm:state=I

executionresult.er:starttime=G

executionresult.er:endtime=H

//links all results to all of the configured testcases in the worksheet.

Accepted answer


permanent link
Mehul Patel (9545) | answered Dec 14 '16, 2:42 a.m.
FORUM MODERATOR
Jeffery,

You can try explicitly linking executionworkitem and executionresult to testcase, it should work. I've modified script as below, it works.

Hope it helps.

Regards,
Mehul

//=========================================

// static test case definition  
testcase.XLSStartRow=2  
testcase.XLSArtifactID=A  
testcase.dc:title=B  
testcase.dc:description=B  

// static configured testcase definition with link to testcase  
executionworkitem.XLSStartRow=2  
executionworkitem.XLSArtifactID=C  
executionworkitem.testcase=Link(A)  // *** explicit linking **** //
executionworkitem.dc:title=D  
executionworkitem.dc:description=D  

// result definition starting at line 2 in the spreadsheet  
executionresult.XLSStartRow=2  
executionresult.XLSArtifactID=E  
executionresult.testcase=Link(A)   // *** explicit linking **** //
executionresult.executionworkitem=Link(C) // *** explicit linking **** //
executionresult.dc:title=F  
executionresult.er:details=F  
executionresult.jzalm:state=I  
executionresult.er:starttime=G  
executionresult.er:endtime=H  

//=========================================
Jeffrey Behnke selected this answer as the correct answer

Comments
Jeffrey Behnke commented Dec 15 '16, 9:44 a.m.

 Mehul,

Thank you for your time and effort to resolve this issue. I have successfully tested on our end and we are now able to successfully import into RQM.

Thank you again.
Jeff

Your answer


Register or to post your answer.