It's all about the answers!

Ask a question

RQMExcelImporter Import multiple testsuites linked to multiple test cases, link testsuites to testplan


Jacob Huang (1535) | asked Aug 22 '13, 10:00 p.m.
retagged Aug 27 '13, 2:59 p.m. by Ralph Earle (25739)
 Hi, I have an excel document that contains multiple test suites and multiple test cases.  Each test suite contains multiple test cases.  Is it possible to create a config file that does the following in a single "Export to Repository":
  1. Import multiple test suites
  2. For each test suite, import associated test cases and link those test cases to the appropriate test suite.
    1. Must not duplicate associated test suite for each test case
  3. Link test suites to existing test plans.
Since each test suite contains multiple test cases, I would like to associate all "bundled" test cases with one copy of its test suite.  So far, I am unable to do the following with a single import:
  1. Link multiple test cases with its single appropriate test suite without duplicating test suites.
  2. Link test suites to existing test plans.
For linking imported test suites to existing test plans, I have tried both syntaxes for specifying an existing testplan via its ID:
testplan.XLSArtifactID="urn:com.ibm.rqm:testplan:1"
Error: Error sending to server "urn:com.ibm.rqm:testplan:1" of type testplan
The remote server returned an error: (400) Bad Request.

testplan.XLSArtifactID=urn:com.ibm.rqm:testplan:1
Error: Configuration File, Line 35. Found a value that reduced to "urn:com.ibm.rqm:testplan:1", but was expecting a value equivalent to a column, cell, or literal.
-------------------------------------------------------------
cfg file below
-------------------------------------------------------------
testcase.XLSStartRow=2
testcase.XLSWorksheetID="Sheet1"

testcase.ID=A
testcase.dc:title=C
testcase.dc:description=B

testsuite.ID=testcase.XLSArtifactID
testsuite.dc:title=testcase.dc:title

testplan.XLSArtifactID="urn:com.ibm.rqm:testplan:1"
testplan.XLSLink=testcase
-------------------------------------------------------------
imitation of excel worksheet below
notes: I would be happy to upload an actual spreadsheet if able
Also, column A values are merged in the spreadsheet
-------------------------------------------------------------
A                                  B                                         C
testsuite1          |          ts1.1                |                   ab
                         |          ts1.2                 |                  cd
testsuite2          |          ts2.1                |                   ef
                          |          ts2.2               |                    gh
                         |           ts2.3                |                   ij



Comments
Jacob Huang commented Aug 23 '13, 9:31 a.m.

By the way, I am using RQMExcelImporter 4.0.0 (CLM 4.0.0.1) 

Accepted answer


permanent link
Diane Everitt (27835) | answered Jan 28 '14, 12:10 p.m.
I tested this extensively using version 4.0.3 and 4.0.5 of the Importer and MS Excel 2010.  Using Link() is supported for Test Plans linking to Test Case per example in Excel best practices pdf .  However, it is not currently supported for Test Suites (Internal Server Error: 500) is encountered.

I hope this helps.

Thank you,
Diane
Jacob Huang selected this answer as the correct answer

5 other answers



permanent link
Hao Wan (1.5k35) | answered Aug 28 '13, 1:41 a.m.
JAZZ DEVELOPER
 Hi Jacob,
1st, XLSArtifactID should work with external, but the value you specified is a type of internal id. you can change it to testplan1 and try again

permanent link
Jacob Huang (1535) | answered Aug 29 '13, 9:12 a.m.
 Hi Hao,

I tried both of the following, and received errors as listed:

Scenario 1
// import testsuites
testsuite.XLSStartRow=2
testsuite.XLSArtifact=A
testsuite.dc:title=A

// create link to existing testplan
testplan.dc:title="urn:com.ibm.rqm:testplan:testplan2"
testplan.XLSLink=testsuite

Error:
Error sending to server test excel import_Sheet 1_2.xml of type testsuite
The remote server returned an error: (500) Internal Server Error.

Scenario 2

// config file contents the same as Scenario 1 except changed the testplan section
// create link to existing testplan
testplan.XLSArtifactID="urn:com.ibm.rqm:testplan:testplan2"
testplan.XLSLink=testsuite

Error:
Error sending to server test excel import_Sheet 1_2.xml of type testsuite
The remote server returned an error: (500) Internal Server Error.

Unless I misunderstood the field I am supposed to change, changing the reference field to "testplan1" or "testplan2" as it is named in our environment, i.e. the name of the test plan, did not work.

permanent link
Collin Zhu (1) | answered Sep 03 '13, 3:52 a.m.
I have the same problem. Any solution for that. I also tried "Link" and "LinkExisting". Neither were working for this case.

permanent link
Maria Amalan (784164) | answered Sep 17 '14, 2:12 a.m.
 I am also facing the same problem. I have used the below syntax, to specific which existing test plan the newly created test cases/suites are supposed to be linked to. It doesn't work. Can someone please help. Thanks.

testplan.XLSArtifactID="urn:com.ibm.rqm:testplan:209"

Comments
Lily Wang commented Sep 17 '14, 4:17 a.m.

Hi Maria,

To link test cases to the existing test plan, you can try something like:
-------------------
testcase.XLSArtifactID=A
testcase.dc:title=B
testcase.dc:description=E
testcase.testplan=LinkExisting("urn:com.ibm.rqm:testplan:209")
-------------------
The Excel Importer best practice document has detail explanation about the "LinkExisting" usage.


Maria Amalan commented Sep 17 '14, 5:24 a.m.

Thank you for your response Lily.

I have tried this code but I am getting "(500) Internal Server Error" 


permanent link
Kumar Kumar (6427) | answered Aug 23 '16, 5:10 a.m.
Is this TestPlan to TestSuite linking issue is solved. Any Idea?

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.