It's all about the answers!

Ask a question

RQM Excel Importer: getting Req' linked to test cases


Homer Pope (15811922) | asked Sep 01 '10, 9:12 a.m.
Hello,
We are starting a large project and are developing our approach for importing assets into RQM as opposed to manual entry for the following assets:
Requirements
Test Case
Test Scripts
I would like to have the following linkage
Requirement->Test case-> Test script
Can this be accomplished using the RQMExcelImporter and what would be the process? Documentation doesnt seem to go to this level.
Many Thanks,
Homer

5 answers



permanent link
Pat Roberto (4111) | answered Sep 02 '10, 1:45 p.m.
Did you look at the samples provided with the install?

My location...C:\Program Files\IBM\RQMExcelImporter\Samples.

HTH

Pat


Hello,
We are starting a large project and are developing our approach for importing assets into RQM as opposed to manual entry for the following assets:
Requirements
Test Case
Test Scripts
I would like to have the following linkage
Requirement->Test case-> Test script
Can this be accomplished using the RQMExcelImporter and what would be the process? Documentation doesnt seem to go to this level.
Many Thanks,
Homer

permanent link
Homer Pope (15811922) | answered Sep 03 '10, 2:52 p.m.
Yes I have but none of the samples give a solution to get everything in one shot. I would like to do the following
Import a test case that creates a test script and links it to an already existing requirement.

Did you look at the samples provided with the install?

My location...C:\Program Files\IBM\RQMExcelImporter\Samples.

HTH

Pat


Hello,
We are starting a large project and are developing our approach for importing assets into RQM as opposed to manual entry for the following assets:
Requirements
Test Case
Test Scripts
I would like to have the following linkage
Requirement->Test case-> Test script
Can this be accomplished using the RQMExcelImporter and what would be the process? Documentation doesnt seem to go to this level.
Many Thanks,
Homer

permanent link
Mike Yalter (11611) | answered Sep 13 '10, 5:12 p.m.
JAZZ DEVELOPER
Hello,
We are starting a large project and are developing our approach for importing assets into RQM as opposed to manual entry for the following assets:
Requirements
Test Case
Test Scripts
I would like to have the following linkage
Requirement->Test case-> Test script
Can this be accomplished using the RQMExcelImporter and what would be the process? Documentation doesnt seem to go to this level.
Many Thanks,
Homer


There is a work item for this functionality, 25869.
There is currently no way of linking more than one type of record together.

permanent link
Todd Weakley (111) | answered Oct 12 '10, 12:06 p.m.
Hello,
We are starting a large project and are developing our approach for importing assets into RQM as opposed to manual entry for the following assets:
Requirements
Test Case
Test Scripts
I would like to have the following linkage
Requirement->Test case-> Test script
Can this be accomplished using the RQMExcelImporter and what would be the process? Documentation doesnt seem to go to this level.
Many Thanks,
Homer


Try using this, I got is from Jazz Forum

//---Requirements
//Start looking for requirements after row 2
requirement.XLSStartRow=2
requirement.XLSArtifactID=A
requirement.dc:title=B
requirement.dc:description=C
//requirement.jzalm:owner=D
//requirement.dc:creator=D

//---Test Scripts
// Start looking for scripts after row 2
testscript.XLSStartRow=2

// use the data in the first row of a found script's column B
// Test script is using the same XLSArtifactID as requirement
testscript.XLSArtifactID=A
testscript.dc:title=E
testscript.dc:description=F

// 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.description=H
testscript.steps.title=G
testscript.steps.name=G
//testscript.steps.expectedResult=F

// a new script starts when we encounter an empty row
testscript.XLSDelimeter=\n

//--- Test Case
// Start looking for test case after row 2
testcase.XLSStartRow=2

// a new test case starts when we encounter an empty row
testcase.XLSDelimeter=\n

//Test case and requirement are having the same XLSArtifactID
// This is for the TestCaseUpdater Utility
//testcase.XLSArtifactID=A
//testcase.XLSArtifactID=D
//testcase.ID=requirement.XLSArtifactID


//Link test case to requirement
//This line will link test case to all requirements in the xls file
//testcase.requirement=requirement.identifier

// Link test case to test script
// self referential links must be declared before also using column definitions
// Below lines will create test case and test script in same name but they can link each other
testcase.dc:title=testscript.dc:title
testcase.dc:description=testscript.dc:description

I used this, and I can import requirements, test cases, and scripts together linked.

Look for TestCase_Req.xls in Jazz

permanent link
Homer Pope (15811922) | answered Oct 12 '10, 12:55 p.m.
Thanks for the suggestion, but it did not work. Let me past in my config file that I have working ( links TC and TS and creates Req, but not linked)

//---Requirements
requirement.XLSArtifactID=B8
requirement.dc:title=B8
requirement.dc:description=B8
//requirement.jzalm:owner
//requirement.dc:creator

//----------

//---Test Scripts
testscript.XLSStartRow=15
testscript.dc:title=B12
testscript.dc:description=B13

// 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.description=B
testscript.steps.title=B
testscript.steps.name=B
testscript.steps.expectedResult=C


// a new script starts when we encounter an empty row
testscript.XLSDelimeter=\n

//----------

//---Test Cases
testcase.dc:title=B2
testcase.dc:description=B3


//---Test Cases and Test Scripts linkage
testscript.XLSArtifactID=B2
testcase.XLSLink=testscript

//Test case and requirement linkage, suggestion from Jazz
testcase.requirement=requirement.identifier


//testcase.dc:title=testscript.dc:title
//testcase.dc:description=testscript.dc:description


testcase.weight="100"
testcase.Author=B5
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCasePreCondition","RQM-KEY-TC-PRE-COND-TITLE")=B6
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCasePostCondition","RQM-KEY-TC-POST-COND-TITLE")=B7
testcase.category term="Category".value=B11




Hello,
We are starting a large project and are developing our approach for importing assets into RQM as opposed to manual entry for the following assets:
Requirements
Test Case
Test Scripts
I would like to have the following linkage
Requirement->Test case-> Test script
Can this be accomplished using the RQMExcelImporter and what would be the process? Documentation doesnt seem to go to this level.
Many Thanks,
Homer


Try using this, I got is from Jazz Forum

//---Requirements
//Start looking for requirements after row 2
requirement.XLSStartRow=2
requirement.XLSArtifactID=A
requirement.dc:title=B
requirement.dc:description=C
//requirement.jzalm:owner=D
//requirement.dc:creator=D

//---Test Scripts
// Start looking for scripts after row 2
testscript.XLSStartRow=2

// use the data in the first row of a found script's column B
// Test script is using the same XLSArtifactID as requirement
testscript.XLSArtifactID=A
testscript.dc:title=E
testscript.dc:description=F

// 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.description=H
testscript.steps.title=G
testscript.steps.name=G
//testscript.steps.expectedResult=F

// a new script starts when we encounter an empty row
testscript.XLSDelimeter=\n

//--- Test Case
// Start looking for test case after row 2
testcase.XLSStartRow=2

// a new test case starts when we encounter an empty row
testcase.XLSDelimeter=\n

//Test case and requirement are having the same XLSArtifactID
// This is for the TestCaseUpdater Utility
//testcase.XLSArtifactID=A
//testcase.XLSArtifactID=D
//testcase.ID=requirement.XLSArtifactID


//Link test case to requirement
//This line will link test case to all requirements in the xls file
//testcase.requirement=requirement.identifier

// Link test case to test script
// self referential links must be declared before also using column definitions
// Below lines will create test case and test script in same name but they can link each other
testcase.dc:title=testscript.dc:title
testcase.dc:description=testscript.dc:description

I used this, and I can import requirements, test cases, and scripts together linked.

Look for TestCase_Req.xls in Jazz

Your answer


Register or to post your answer.