Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Limitation on Test Case ID Length when importing Test Case Execution Record from Excel into RQM

Questions
Tags
Users
Badges
Nadra Rafee
(45●9●27) edited
Jun 11 '17, 11:33 p.m.

Environment: RQM 6.0.3, RQM Import Utility, Windows 7, Excel 2013

When testing the import of Test Cases, Test Scripts, and Test Case Execution Records using the RQM import utility, I found that there is a limit of 3 characters on the Test Case ID to have successful import of the Execution Record.

If the Test Case ID is more than 3 characters, the Execution Record is imported at the Test Case level not the test results at the Test Step level.

Can you please confirm or advise the Test Case ID length limitation?

Thank you.

0 votes

Comments
Don Yang
Jun 12 '17, 5:25 a.m.
Hi, Nadra What kind of id are you referring to? If you have a cfg file, please provide the details on what you have done linking to the different result(the Execution Record is imported at the Test Case level not the test results at the Test Step level.?) if you use any sample xls/cfg, please provide the name and what you changed to test leading to your finding/conclusion?

Nadra Rafee
Jun 12 '17, 11:14 a.m.
Hi Don, I don't think I am able to attach the files here but here is the information of the excel & config files. Note that the test case ID (in Col A) initially included: <TC001_Setup User Preferences_View Preferences screen> The import of test cases & test scripts worked but test execution result was not getting imported (at the step level). When I changed the value in Col A to <TC1>, the execution result import worked. Please advise if there any limitation on the length of the test case ID when importing the test execution results. Excel sheet Col A: Test Case ID Col B: Test Case Description Col E: Test Step ID/Name Col F: Test Step Description Col G: Expected Result Col H: Actual Result Col I: Test Status Col J: Tester Col K: Comments Config file to follow ..

Nadra Rafee
Jun 12 '17, 11:17 a.m.
Config File testscript.XLSWorksheetID="TC Results" testscript.XLSStartRow=2 testscript.XLSArtifactID=A testscript.dc:title=A testscript.dc:description=B testscript.steps.type="Reporting" testscript.steps.description=F testscript.steps.title=E testscript.steps.name=E testscript.steps.expectedResult=G testscript.steps.comment=K testscript.XLSDelimeter=\n testcase.XLSWorksheetID="TC Results" testcase.XLSStartRow=2 testcase.dc:title=testscript.dc:title testcase.dc:description=testscript.dc:description testcase.XLSArtifactID=A //testcase.priority=N testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCaseDesign","RQM-KEY-TC-DESIGN-TITLE")=B executionworkitem.XLSWorksheetID="TC Results" executionworkitem.XLSStartRow=2 executionworkitem.XLSDelimeter=\n executionworkitem.XLSArtifactID="executionworkitem_" & A executionworkitem.dc:title=A executionworkitem.testcase=Link(A) .. to continue

Nadra Rafee
Jun 12 '17, 11:18 a.m.
Conf File (Continued) executionresult.XLSWorksheetID="TC Results" executionresult.XLSStartRow=2 executionresult.XLSDelimeter=\n executionresult.dc:title=executionworkitem.dc:title executionresult.er:details=F executionresult.jzalm:state=I executionresult.er:stepResults.steptitle=E executionresult.er:stepResults.stepname=E executionresult.er:stepResults.er:steptype="Reporting" executionresult.er:stepResults.er:result=I executionresult.er:stepResults.er:description=F executionresult.er:stepResults.er:expectedResult=G executionresult.er:stepResults.er:actualResult=H executionresult.er:stepResults.er:tester=J executionresult.testcase=Link(E) executionresult.testscript=Link(A)

1 answer
5,917 views
0 votes

Accepted answer

Permanent link
Mehul Patel
FORUM MODERATOR (969●5) Jun 14 '17, 7:06 a.m.

Nadra,


No, there is not such limitation related to Testcase ID length. But we fixed some defect in 604 where execution results were not getting linked if the ID contains while space (https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/158053), check with v604 if that solves described problem.

Regards,
Mehul

Nadra Rafee selected this answer as the correct answer

0 votes

Comments
Nadra Rafee
Jun 14 '17, 10:05 a.m.
Thank you for your answer. To verify, I will need to upgrade RQM to 6.0.4 to work with the upgraded import utility. When I test again and find issues, will raise a new question.

Your answer

Register or log in 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.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12,145
× 22

Question asked: Jun 11 '17, 11:32 p.m.

Question was seen: 5,917 times

Last updated: Jun 14 '17, 10:05 a.m.

Confirmation Cancel Confirm