Importing a testcase and linking it to an existiing testsuite
![]()
Hi,
I am trying to import testcases via ecxelimport utility that are linked to existing testscripts AND to existing testsuites. I managed to link the existing script to the testcase, but I failed with the testsuite. Here is what I tried: testcase.XLSStartRow=6 testcase.priority=A testcase.dc:title=C testcase.jzalm:owner=D testcase.dc:description=E testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCasePreCondition","RQM-KEY-TC-PRE-COND-TITLE")=F testcase.testscript=Link("urn:com.ibm.rqm:testscript:"&G) testcase.testsuite=Linkexisting("urn:com.ibm.rqm:testsuite:"&H) but when I generate the XML file, there is no mention of the testsuite. The linking to the testscript works great. What should I do? |
2 answers
![]()
Hi,
Did you try to export the excel directly to the server instead of generating the xml? Does the linking show up when you use export to repository option Comments Hi I tried both, via export and import and via direct upload to the repository. Both do not work I am using the importer utility version 6 with a RTC in Version 5.0.1. When generating the XML, I see that this line :testcase.testsuite=Linkexisting("urn:com.ibm.rqm:testsuite:"&H) is not transformed at all, no mention of a testsuite in the file. The suite had been manually created. Thanks for your help
I had tried v5.0.1 and 5.0.2 ExcelImporter with v5.0.1 RQM with no problem. In theory v6.0 Importer is not compatible with v5.0.1 RQM. you may want to try with v5.0.2 excelimporter given that your RQM is 5.0.1.
HI Don, thanks for your answer. I have tried all of the suggested: deinstall 6.0, install 5.0.2, and also I tried to exacly use one id for the suite as suggested by you. Still, no mention of the testsuite in the generated XML file. my cfg file is by now:
testcase.dc:title=A
And all works well except for the last row. If you say it works with you - what exact cfg are you using? I used sample TestSuite with TestCases 001.cfg
HI Dan, I also just tried the non changed version of the TestSuite with TestCases 001.cfg and actually it looks different to what you have above: it is meant to create a testsuite including testcases, testsuite.XLSLink=testcase, but not link to an existing. When I try your approach, I see in the XML the standard HREF, same as for the link to the script... and it does not work when importing it into RQM. Which makes sense to me, as in case of script I link to a child, whereas for the suite, I link to a master. Following this, it seems absolutely meaningful, when I try to create a new testsuite (as is in the above) I get another XML file for the testsuite, that then links the testcases to the suite. However, I did not find a place where to import the testsuite xml. - do you know where? And also, it does not resolve my problem with the link to the existing suite. Can you maybe post your complete cfg and all of the xml files that you import?
HI,
testsuite.XLSLink=testcase The cfg I posted is exactly what I tested with for my end user and it works for my RQM5.0.2+ExcelImporter5.0.2. I exported to RQM project directly. As you can see, I commented out testsuite creation part because I want to link the created test cases(from importer) to the existing test suite, hence using testcase.testsuite=LinkExisting(M7)
Hi, this worked, thank you! This was the necessary hint! see below
showing 5 of 9
show 4 more comments
|
![]() HI Dan, thanks a lot for your help, your last answer helped me. So for everybody else: it might be a problem with creating teststuites, but if you want to import testcases and link them to an existing testsuite, make sure to only include the inkexisting part and comment out the part with the testsuite reference. Also it is necessary to import via direct rqm import. My complete and working CFG is then: testcase.XLSStartRow=6
testcase.dc:title=A
|
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
what is ExcelImporter and RQM version?
is your test suite manually created on GUI or it was imported by ExcelImporter?