What is the order in which test cases get imported in RQM from Excel sheet
We are on 6.0.1 version and using RQMExcel importer to import test cases from Excel to RQM.
We have notices that the test cases does not get imported in the same order as they are written in the excel sheet.
On what order the export plulg-in pick test case from excel, is is starting from the top row and moving towards the bottom rows of the sheet?
We have notices that the test cases does not get imported in the same order as they are written in the excel sheet.
On what order the export plulg-in pick test case from excel, is is starting from the top row and moving towards the bottom rows of the sheet?
2 answers
There was a similar issue which was fixed in 6.0.2 via the following workitem
QM: Excel/Word import issue: Test Case Results are imported out of order
You may want to download the 6.0.2 version of the utility and see if it addresses the issue you are seeing
QM: Excel/Word import issue: Test Case Results are imported out of order
You may want to download the 6.0.2 version of the utility and see if it addresses the issue you are seeing
Comments
Doesn't seems to work for
<g class="gr_ gr_47 gr-alert gr_gramm gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" data-gr-id="47" id="47">
test
</g>
case and test script.
I have updated this
<g class="gr_ gr_53 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="53" id="53">
workitem
</g>
with my observation.
There is no direct way to export the association between test case, requirement and test script in just one go. This can be achieved by applying these two steps.
Step 1: Use the attached Excel and CFG sample to export Test Case, Requirement and Test Script from MS Excel to Rational Quality Manager
Step 2: Update all test cases in a project to link to a requirement that has the same ID
Comments
Rohit Rishabh
Oct 04 '17, 7:06 p.m.Here is my configuration file the we use:
// 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 from row 2
testscript.XLSStartRow=2
// use the data in the first row of a found script's column B
testscript.XLSArtifactID=B
testscript.dc:title=D
testscript.dc:description=C
testscript.category term="Product".value=J
// 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=E
testscript.steps.description=E
testscript.steps.expectedResult=F
// 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=B
testcase.dc:description=testscript.dc:description
//adding test case category values
testcase.category term="1. Project Team".value=H
testcase.category term="2. Release".value=I
testcase.category term="3. Product".value=J
testcase.category term="4. Module".value=K
testcase.category term="5. Function".value=L
testcase.category term="6. Test Phase".value=M
testcase.category term="8. Usage Frequency".value=Q
testcase.category term="9. Type of Change".value=R
testcase.category term="10. Design Complexity".value=P
testcase.category term="11. Risk".value=S
testcase.priority=O
//adding test case attribute values
testcase.customAttributes identifier="SR_Number".name="SR Number".type="MEDIUM_STRING".value=G