It's all about the answers!

Ask a question

Getting error 500 while importing TCER and Test Result with Test case and Script using excel importer


Rohit Rishabh (1531136) | asked Jun 20 '17, 5:59 p.m.
edited Jun 20 '17, 6:04 p.m.

We are trying to import Test Case, Test Script, TCER and Test Result referring the sample available with RQM Excel importer.
While we are able to successfully import Test Case and Test Script, we are getting error 500 for TCER and Test Result.

Here is our .cfg file

// This configuration file creates a test case with each test script and links them.
// The linking is accomplished by self referential data
// Start looking for scripts from row 2
testscript.XLSStartRow=2

// use the data in the first row of a found script's column B
testscript.XLSArtifactID=B
testscript.dc:title=D
testscript.dc:description=C
testscript.category term="Product".value=J


// the literal "execution" will be put into the step type tag, so all steps will be of type execution
testscript.steps.type="execution"
testscript.steps.title=E
testscript.steps.description=E
testscript.steps.expectedResult=F

// a new script starts when we encounter an empty row
testscript.XLSDelimeter=\n
   
// we want to use the data we got for each test script to create a test case
testcase.ID=testscript.XLSArtifactID


// by refering to the testscript's field instead of the column that data comes from
// the tool will also create links to each of the test scripts.
testcase.dc:title=B
testcase.dc:description=testscript.dc:description

//adding test case category values
testcase.category term="1. Project Team".value=H
testcase.category term="2. Release".value=I
testcase.category term="3. Product".value=J
testcase.category term="4. Module".value=K
testcase.category term="5. Function".value=L
testcase.category term="6. Test Phase".value=M
testcase.category term="8. Usage Frequency".value=Q
testcase.category term="9. Type of Change".value=R
testcase.category term="10. Design Complexity".value=P
testcase.category term="11. Risk".value=S
testcase.priority=O

//adding test case attribute values
testcase.customAttributes identifier="SR_Number".name="SR Number".type="MEDIUM_STRING".value=G

//execution workitem
executionworkitem.XLSStartRow=2
executionworkitem.XLSDelimeter=\n
executionworkitem.XLSArtifactID="executionworkitem_" & B
executionworkitem.dc:title=B
executionworkitem.testcase=Link(B)

//execution result

executionresult.XLSStartRow=2
executionresult.XLSDelimeter=\n
executionresult.dc:title=executionworkitem.dc:title
executionresult.er:details=E
executionresult.jzalm:state=V
executionresult.er:starttime=U
executionresult.er:endtime=W
executionresult.er:stepResults.steptitle=D
executionresult.er:stepResults.stepname=D

executionresult.er:stepResults.er:steptype="execution"
executionresult.er:stepResults.er:result=T
executionresult.er:stepResults.er:description=E
executionresult.er:stepResults.er:expectedResult=F
executionresult.er:stepResults.er:actualResult=F
executionresult.testcase=Link(B)
executionresult.testscript=Link(B)

below is the the image of our excel template (Plz right click and download the image for clarity)

Can someone help in finding out what is going wrong here?

2 answers



permanent link
Don Yang (7.7k21109138) | answered Jun 20 '17, 8:21 p.m.

Hi, Rohit

From the cfg file, it does not show any problem as it seems to be similar with the sample.
Do you also have the same problem when importing the sample you refer to? I guess you would.
In some version of ExcelImporter, there is problem in the order to export the artifacts into RQM hence leading to 500 error. What version of RQM and RQMExcelImporter do you have now?
If you import the same xls/cfg once again, do you see the same problem?
if you close ExcelImporter and then try to import again, do you see the same issue?
Can you please paste the export window with 500 error trace here?


Comments
Rohit Rishabh commented Jun 21 '17, 11:34 a.m.

Hi Don,

I haven't imported the sample as the columns in the sample excel does not match our RQM configuration.
I am using 601 version of RQMExcelImporter
I imported the same xls/cfg and got the same problem


Don Yang commented Jun 21 '17, 7:57 p.m.

Please try with a sample you referred to (to create your own excel and cfg files) and see if you got the same issue or not. The log trace does not show the evidence of old version of known issue(export order causing the problem) and v6.0.1 is quite recent version.
If you dont have same issue with the sample, pls let us know which sample you are referring to and what configuration you have changed and what part of excel file you have changed to your own use case so that we may be able to find out what is wrong.


permanent link
Rohit Rishabh (1531136) | answered Jun 21 '17, 11:35 a.m.

Here is the 500 error trace:
6/21/2017 10:31:21 AM:



6/21/2017 10:31:21 AM:
SESSION: 6/21/2017 10:31:21 AM

6/21/2017 10:31:21 AM: Getting artifacts from current document Test Case Test Script TCER Test Result.xlsx
6/21/2017 10:31:22 AM: Created 8 artifacts, sending to server
6/21/2017 10:31:22 AM: sending testscript0 named Sample_test_case2_name_containing_white_space
6/21/2017 10:31:25 AM: Server returned code Created
6/21/2017 10:31:25 AM: sending testscript1 named Sample_test_case1_name_containing_white_space
6/21/2017 10:31:26 AM: Server returned code Created
6/21/2017 10:31:26 AM: sending testcase2 named Sample_test_case2_name_containing_white_space
6/21/2017 10:31:27 AM: Server returned code Created
6/21/2017 10:31:27 AM: sending testcase3 named Sample_test_case1_name_containing_white_space
6/21/2017 10:31:28 AM: Server returned code Created
6/21/2017 10:31:28 AM: sending executionworkitem4 named executionworkitem_Sample_test_case2_name_containing_white_space
6/21/2017 10:31:29 AM: Server returned code InternalServerError
6/21/2017 10:31:29 AM: Error sending to server executionworkitem_Sample_test_case2_name_containing_white_space of type executionworkitem
6/21/2017 10:31:29 AM: Internal Server Error
6/21/2017 10:31:29 AM: sending executionworkitem5 named executionworkitem_Sample_test_case1_name_containing_white_space
6/21/2017 10:31:29 AM: Server returned code InternalServerError
6/21/2017 10:31:29 AM: Error sending to server executionworkitem_Sample_test_case1_name_containing_white_space of type executionworkitem
6/21/2017 10:31:29 AM: Internal Server Error
6/21/2017 10:31:29 AM: sending executionresult6 named executionworkitem_Sample_test_case2_name_containing_white_space
6/21/2017 10:31:30 AM: Server returned code BadRequest
6/21/2017 10:31:30 AM: Error sending to server executionworkitem_Sample_test_case2_name_containing_white_space of type executionresult
6/21/2017 10:31:30 AM: Bad Request
6/21/2017 10:31:30 AM: sending executionresult7 named executionworkitem_Sample_test_case1_name_containing_white_space
6/21/2017 10:31:30 AM: Server returned code BadRequest
6/21/2017 10:31:30 AM: Error sending to server executionworkitem_Sample_test_case1_name_containing_white_space of type executionresult
6/21/2017 10:31:30 AM: Bad Request
6/21/2017 10:31:30 AM: finished writing artifacts

Your answer


Register or to post 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.