It's all about the answers!

Ask a question

Why Import Errors in 3.0.1 ExcelImportUtility??


tina fusari (3643) | asked Jun 15 '11, 1:16 p.m.
My config file executes fine RQM's 2.0 ExcelImportUtility except that the
Test Plan won't link to the Test Cases and now that I've upgraded to 3.0.1 ExcelImportUtility I get all these errors. Why do these errors occur in the new version of the Excel Import utility and not the old one?

Initializing.....
Reading Configuration File....
Getting artifacts from document.....
Sending artifacts to https://xxxxx
Sending testscript 0 named 2._Rollback_Legacy_Preservation_Testing...
Sending testcase 1 named 2._Rollback_Legacy_Preservation_Testing...
Error sending to server 2._Rollback_Legacy_Preservation_Testing of type testcase
Sending testscript 2 named Option_Lock_Category...
Sending testcase 3 named Option_Lock_Category...
Error sending to server Option_Lock_Category of type testcase
Sending testscript 4 named Bypass_Rollover_Category...
Sending testcase 5 named Bypass_Rollover_Category...
Error sending to server Bypass_Rollover_Category of type testcase
Sending testplan 6 named Bypass_Rollover_Category.xml...
Exporting completed with 3 failures!
Detailed log file at: C:\Documents and Settings\vhaiswfusart\Application Data\Mso2Rqm\129526311636232757 log.txt

Here is the config file:


// this configuration file will create a static testplan and a testase object for each one listed
// and link all testcase to the testplan



testplan.dc:title=C1
testplan.Section("myns:com.ibm.rqm.planning.editor.section.planBusinessObjectives","RQM-KEY-TP-BUSS-OBJ-TITLE")=C2
testplan.Section("myns:com.ibm.rqm.process.web.entryCriteria","RQM-KEY-PROC-ENTRY-CRITERIA-TITLE")=C3
testplan.Section("myns:com.ibm.rqm.process.web.exitCriteria","RQM-KEY-PROC-EXIT-CRITERIA-TITLE")=C4
testplan.XLSLink=testcase



// 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 starting at row 7
testscript.XLSStartRow=7

// use the data in the first row of a found script's column B
testscript.XLSArtifactID=B
testscript.dc:title=B
testscript.description=Pre(E)

// 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=Pre(H)
testscript.steps.title=G
testscript.steps.name=G
testscript.steps.expectedResult=Pre(I)

// *set testscript state to "Approved" * //
testscript.alm:state ="com.ibm.rqm.planning.common.approved"
//testscript.alm:state="com.ibm.rqm.planning.common.underreview"
testscript.alm:description ="This is my new description"


// 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.
// set testcase state to "Approved" * //
testcase.alm:state="com.ibm.rqm.planning.common.approved"
testcase.dc:title=testscript.dc:title
testcase.dc:description=E
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCaseDesign","Test Case Design")=Pre(E)

// * set category values */
testcase.category term="Category".value=J1
testcase.category term="Test Phase".value=J2
testcase.category term="Test Activity".value=J3
testcase.XLSLink=testscript

One answer



permanent link
Paul Slauenwhite (8.4k12) | answered Jun 16 '11, 6:48 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
My config file executes fine RQM's 2.0 ExcelImportUtility except that the
Test Plan won't link to the Test Cases and now that I've upgraded to 3.0.1 ExcelImportUtility I get all these errors. Why do these errors occur in the new version of the Excel Import utility and not the old one?

Initializing.....
Reading Configuration File....
Getting artifacts from document.....
Sending artifacts to https://xxxxx
Sending testscript 0 named 2._Rollback_Legacy_Preservation_Testing...
Sending testcase 1 named 2._Rollback_Legacy_Preservation_Testing...
Error sending to server 2._Rollback_Legacy_Preservation_Testing of type testcase
Sending testscript 2 named Option_Lock_Category...
Sending testcase 3 named Option_Lock_Category...
Error sending to server Option_Lock_Category of type testcase
Sending testscript 4 named Bypass_Rollover_Category...
Sending testcase 5 named Bypass_Rollover_Category...
Error sending to server Bypass_Rollover_Category of type testcase
Sending testplan 6 named Bypass_Rollover_Category.xml...
Exporting completed with 3 failures!
Detailed log file at: C:\Documents and Settings\vhaiswfusart\Application Data\Mso2Rqm\129526311636232757 log.txt

Here is the config file:


// this configuration file will create a static testplan and a testase object for each one listed
// and link all testcase to the testplan



testplan.dc:title=C1
testplan.Section("myns:com.ibm.rqm.planning.editor.section.planBusinessObjectives","RQM-KEY-TP-BUSS-OBJ-TITLE")=C2
testplan.Section("myns:com.ibm.rqm.process.web.entryCriteria","RQM-KEY-PROC-ENTRY-CRITERIA-TITLE")=C3
testplan.Section("myns:com.ibm.rqm.process.web.exitCriteria","RQM-KEY-PROC-EXIT-CRITERIA-TITLE")=C4
testplan.XLSLink=testcase



// 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 starting at row 7
testscript.XLSStartRow=7

// use the data in the first row of a found script's column B
testscript.XLSArtifactID=B
testscript.dc:title=B
testscript.description=Pre(E)

// 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=Pre(H)
testscript.steps.title=G
testscript.steps.name=G
testscript.steps.expectedResult=Pre(I)

// *set testscript state to "Approved" * //
testscript.alm:state ="com.ibm.rqm.planning.common.approved"
//testscript.alm:state="com.ibm.rqm.planning.common.underreview"
testscript.alm:description ="This is my new description"


// 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.
// set testcase state to "Approved" * //
testcase.alm:state="com.ibm.rqm.planning.common.approved"
testcase.dc:title=testscript.dc:title
testcase.dc:description=E
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCaseDesign","Test Case Design")=Pre(E)

// * set category values */
testcase.category term="Category".value=J1
testcase.category term="Test Phase".value=J2
testcase.category term="Test Activity".value=J3
testcase.XLSLink=testscript


A couple of questions:

1. Can you post the contents of the C:\Documents and Settings\vhaiswfusart\Application Data\Mso2Rqm\Mso2Rqm_Debug.log file?

2. Can you post the contents of your Excel file?

3. Can you try RQM >> Export to File in Excel and post the contents of:

2._Rollback_Legacy_Preservation_Testing
Option_Lock_Category
Bypass_Rollover_Category

4. What version is the RQM sever?

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.