RQM 6.0.2 - Cannot find the sample test cases under the test plan after importing them from XML
I am a newbie to RQM. I am trying the samples that came with the RQM-Extras-RQMExcelWordImporter-6.0.2 utility.
I imported the five test cases from this folder: ..\Documents\excel export\testcase- TestPlan_with_TestCases_001_Acme_Hammers_1.xml TestPlan_with_TestCases_001_Acme_Hammers_2.xml TestPlan_with_TestCases_001_Acme_Hammers_3.xml TestPlan_with_TestCases_001_Acme_Hammers_4.xml TestPlan_with_TestCases_001_Acme_Hammers_5.xml Contents of one of the above xml: <?xml version="1.0" encoding="utf-8"?> <testcase xmlns="http://jazz.net/xmlns/alm/qm/v0.1/" xmlns:jzalm="http://jazz.net/xmlns/alm/v0.1/" xmlns:alm="http://jazz.net/xmlns/alm/v0.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:myns="http://mydomain.net/some/custom/namespace/v0.1/" xmlns:ts="http://jazz.net/xmlns/alm/qm/v0.1/testscript/v0.1/" xmlns:er="http://jazz.net/xmlns/alm/qm/v0.1/executionresult/v0.1" xmlns:vg="http://schema.ibm.com/vega/2008/" xmlns:rs="http://jazz.net/xmlns/alm/qm/remotescript/v0.1/" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:x="urn:schemas-microsoft-com:office:excel"> <myns:com.ibm.rqm.planning.editor.section.testCaseDesign extensionDisplayName="RQM-KEY-TC-DESIGN-TITLE">Start furnace Wait until it hits 10000 degrees Toss in hammer Send in coyote to check on hammer Stop and cool down furnace Ensure hammer looks good (coyote looks a little crispy is acceptable)</myns:com.ibm.rqm.planning.editor.section.testCaseDesign> <dc:title>Hot Hammer</dc:title> <myns:com.ibm.rqm.planning.editor.section.testCasePreCondition extensionDisplayName="RQM-KEY-TC-PRE-COND-TITLE">Hammer must exist</myns:com.ibm.rqm.planning.editor.section.testCasePreCondition> <myns:com.ibm.rqm.planning.editor.section.testCasePostCondition extensionDisplayName="RQM-KEY-TC-POST-COND-TITLE">Hammer must still exist</myns:com.ibm.rqm.planning.editor.section.testCasePostCondition> <dc:description>Hammer introduced to 10000 degrees from a blow furnace</dc:description> <jzalm:owner>ADMIN</jzalm:owner> </testcase> All five imported successfully to the cloud sandbox RQM but i could never see them in RQM. I am using the sandbox https://jazz.net/sandbox02-qm/ and RQM 6.0.2. I read on this forum that we have to import the test cases first and then the test plan so I imported the test plan next which is also imported successfully but I still cannot see the test cases under this test plan in RQM. Contents of the test plan xml, these were exported via Excel Add-in RQMExcelImporter version 6.0.2 19868 ..\Documents\excel export\testplan\TestPlan_with_TestCases_001_Acme_Hammers_1.xml : <?xml version="1.0" encoding="utf-8"?> <testplan xmlns="http://jazz.net/xmlns/alm/qm/v0.1/" xmlns:jzalm="http://jazz.net/xmlns/alm/v0.1/" xmlns:alm="http://jazz.net/xmlns/alm/v0.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:myns="http://mydomain.net/some/custom/namespace/v0.1/" xmlns:ts="http://jazz.net/xmlns/alm/qm/v0.1/testscript/v0.1/" xmlns:er="http://jazz.net/xmlns/alm/qm/v0.1/executionresult/v0.1" xmlns:vg="http://schema.ibm.com/vega/2008/" xmlns:rs="http://jazz.net/xmlns/alm/qm/remotescript/v0.1/" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:x="urn:schemas-microsoft-com:office:excel"> <myns:com.ibm.rqm.planning.editor.section.planBusinessObjectives extensionDisplayName="RQM-KEY-TP-BUSS-OBJ-TITLE">Ensure that the big hammer has all the functionality expected by out clients</myns:com.ibm.rqm.planning.editor.section.planBusinessObjectives> <dc:title>Big Plan</dc:title> <testcase href="../testcase/TestPlan_with_TestCases_001_Acme_Hammers_1.xml"/> <testcase href="../testcase/TestPlan_with_TestCases_001_Acme_Hammers_2.xml"/> <testcase href="../testcase/TestPlan_with_TestCases_001_Acme_Hammers_3.xml"/> <testcase href="../testcase/TestPlan_with_TestCases_001_Acme_Hammers_4.xml"/> <testcase href="../testcase/TestPlan_with_TestCases_001_Acme_Hammers_5.xml"/> </testplan> Where did the test cases go???? |
One answer
They didn't go anywhere.
When you use the RQM Excel Importer, there are two options - Export to Server, and Export to XML file. The first option will create test artifacts on the RQM server (you will need to log on to the server first, just a hint). The second option will generate XML files representing the test artifacts - it's the files that you are looking at. They are on your local machine and have not been posted to the RQM server, and that's why you cannot see any new sample test artifacts. Comments
Neeta Valera
commented May 09 '16, 7:29 a.m.
I know they are on my local machine because I exported them to XML using the RQM Excel Importer. My question is regarding importing them into RQM using the import options within RQM. I imported the XML files into RQM for both the test plan and test cases but I do not see the test cases in RQM I can only see the test plan.
Donald Nong
commented May 09 '16, 9:20 p.m.
I don't quite understand what you are doing. Did you export the Excel content to XML files using the RQM Excel Importer, then upload those XML files into the RQM Web GUI? If so, why don't you use the Export to Server option in the Excel Importer?
Neeta Valera
commented May 11 '16, 9:54 a.m.
Thanks for your response. Yes, that is what I did - export to XML and then Import into RQM Web GUI in the sandbox on the cloud. The Export to Server option does not work with the sandbox. I don't know if it mattrs how the test plans/test cases are imported into RQM, both the options would use the same config file. The problem is the test cases are not linked with the test plans, the test scripts do not link with the test cases. I tried other samples that came with the importer/exporter utility and the same thing happens, the work items are not linked in RQM when imported from the XML.
Donald Nong
commented May 12 '16, 2:15 a.m.
You cannot do it that way. You notice the link in the Test Plan XML file, such as
<testcase href="../testcase/TestPlan_with_TestCases_001_Acme_Hammers_1.xml"/>It does not point to any existing test case at all. You will need to replace it with the corresponding test case that you previously imported. For example, in my case, the ID of the first test case is https://jazz.net/sandbox02-qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/Donald+Nong%27s+Project+%28Quality+Management%29/testcase/slug__qzNxsBgEEeaee_rcuat45Q . Once I replace the Test Case IDs with the correct ones, import the Test Plan XML file and the resulting Test Plan has all the Test Cases linked. The Excel Importer will do this automatically when you export to the server directly. If you really want to try out the Excel Importer, you'd better set up an RQM server locally.
Neeta Valera
commented May 17 '16, 7:59 a.m.
Thanks for your reply, Donald. I cannot access the link you have mentioned above to look at the sample, I get this error (only partial posted, its too big to post):
Can you please post the section of your sample config file that demonstrates what value should be set for the test case id so it can link with the test plan? Thanks for your reply, Donald. I cannot access the link you have mentioned above to look at the sample, I get this error (only partial posted, its too big to post):
Donald Nong
commented Jun 22 '16, 5:01 a.m.
The link in my post is for a test artifact in my jazz.net sandbox project and you don't have access to it. And it does not add any values even you have access to. I simply used the samples the come with the Importer and you should have the same file. My point is the you should export to the server directly and the Importer will fix up all the necessary links and IDs for you. If you export to files first, you will have to manually modify the files one by one.
showing 5 of 7
show 2 more comments
|
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.