RQM: Excel Importer: Cannot import pre-conditions
Hi,
I'm having problems trying to import preconditions using the Excel Importer tool. I have used the following line in the script for pre-conditions: testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCasePreCondition","RQM-KEY-TC-PRE-COND-TITLE")=G After having imported the test cases and test scripts, I go to RQM to see if everything was importer correctly, but when I look at the preconditions I found the following text: %3Cdiv xmlns="http%u003A//www.w3.org/1999/xhtml" xmlns%u003Ao="urn%u003A//schemas-microsoft-com%u003Aoffice%u003Aoffice" xmlns%u003Ast1="urn%u003A//schemas-microsoft-com%u003Aoffice%u003Asmarttags" xmlns%u003Av="urn%u003A//schemas-microsoft-com%u003Avml" xmlns%u003Aw="urn%u003A//schemas-microsoft-com%u003Aoffice%u003Aword"%3EA video is streamming.%3C/div%3E Does anyone knows what could be the problem? Thanks |
6 answers
i am using excel 2010 and on the other PC I have is excel 2007. here is the script we use, have look and see if we are doing anything different to you:
// 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 after row 2
testscript.XLSStartRow=2
// use the data in the first row of a found script's column A
testscript.XLSArtifactID=A
testscript.dc:title=D
testscript.dc:description=M
testscript.category term="Test Phase".value=E
testscript.category term="Test Area".value=F
testscript.category term="Sub Test Area".value=G
// testscript.category term="Change Item".value=H
testscript.customAttributes identifier="Deadlines".name="Deadlines".type="SMALL_STRING".value=J
testscript.customAttributes identifier="Test_Data_Location".name="Test Data Location".type="SMALL_STRING".value=L
testscript.customAttributes identifier="Originating_RMT_File".name="Originating RMT File".type="SMALL_STRING".value=C
testscript.customAttributes identifier="Originating_RMT_File_Location".name="Originating RMT File Location".type="SMALL_STRING".value=B
// 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=O
testscript.steps.title=N
testscript.steps.name=N
testscript.steps.expectedResult=P
// 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=testscript.dc:title
testcase.dc:description=testscript.dc:description
testcase.category term="Test Phase".value=E
testcase.category term="Test Area".value=F
testcase.category term="Sub Test Area".value=G
testcase.category term="Change Item".value=H
testcase.weight="100"
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCasePreCondition", "RQM-KEY-TC-PRE-COND-TITLE")=I
Comments
Gonzalo Garcia Favre
commented Feb 27 '13, 12:20 p.m.
Thanks for your help Anthony. I don't find any difference between both configuration files, but I don't know why it works for you and I have a different result executing that line. thanks for all your help
|
This is the entire config file
////////////////////////////////////Script Configuration // Start looking for scripts after row 2 testscript.XLSStartRow=2 testscript.dc:title=B 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.title=B testscript.steps.description=K testscript.steps.expectedResult=L testscript.XLSDelimeter=\n ////////////////////////////////////Test Case Configuration // Start looking for scripts after row 2 //testcase.XLSStartRow=2 testcase.dc:title=testscript.dc:title testcase.dc:description=testscript.dc:description testcase.weight="1" testcase.category term="Applicable devices".value="All" testcase.category term="Project".value="Project X" testcase.category term="Release".value="Release X" testcase.category term="Feature".value=N testcase.category term="Execution Type".value="Manual" testcase.category term="Test Scenario".value="Normal" testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCasePreCondition","RQM-KEY-TC-PRE-COND-TITLE")=G // a new Test starts when we encounter an empty row testcase.XLSDelimeter=\n |
hi Gonzalo,
what's the value in the excel document in column G? Comments
Gonzalo Garcia Favre
commented Feb 27 '13, 7:16 a.m.
Its a text string: E.g.:
|
Hi I run the same script and the preconditions look fine for us. What version of the migration tool are you running. We are using 4.01 and our RQM version is 4.0.
The line we use is
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCasePreCondition", "RQM-KEY-TC-PRE-COND-TITLE")=I
And the only difference I can tell with yours is we have a space between , and "RQM-KEY....
Comments
Gonzalo Garcia Favre
commented Feb 27 '13, 8:27 a.m.
I have the RQMExcelImporter Version: 1.0.4529.9380 and using RQM 4.0.
Anthony Paul
commented Feb 27 '13, 8:40 a.m.
Anthony Paul
commented Feb 27 '13, 8:41 a.m.
If you get a weird access denied message from that link try this one:
Gonzalo Garcia Favre
commented Feb 27 '13, 10:09 a.m.
Thanks Anthony. I've download the latest version (4.0.1.9638) and tried to import again using "test" as the string to be imported in pre-conditions but got the same result:
|
I am sort of out of ideas. out of curiosity what is www.w3.org, where is it getting that from
Maybe take the "Scripts that create testcases" excel template add a new column at the end for the pre condition and try again.
Maybe there is something up with the excel sheet you are using.
Comments
Gonzalo Garcia Favre
commented Feb 27 '13, 10:47 a.m.
Hi Anthony. What version of Excel are you using?
|
I am trying to export test cases using RQM Excel Importer, I have modified the configuration file according to my Test Case sheet.
I have Test Team Member access on the project Area.
|
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.
Comments
are the test cases linked to any test suite? It will be much more helpful, if you could post your entire script. Thanks
I paste the script below. I couldn't pasted it here