Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

RQMExcelWordImporter TestSuite need to rename the xls file to reimport

Questions
Tags
Users
Badges
w h
(19●18●24) edited
Mar 19 '14, 9:36 a.m.

Using RQM Excel (XLS) Importer 4.0.3 with 4.0.3 RQM server.  Wanted to see if this behavior is by design or a defect, could not find it in forum or the FAQ: https://jazz.net/wiki/bin/view/Main/FrequentlyAskedQuestions

We're in design phase of our test automation and using the Test Suite(TS) linked to Test Cases (TC) import functionality in one XLS. 

1. It looks like we can initially import TS and TCs

2. When we delete the test suite and test cases from RQM and rerun the test, it appears the test cases import but not the test suite. 

3. We rename the test suite name in the XLS and it still does not import. 

4. Only when we rename the XLS file, the test suite will reimport. 

5. If we change the name of the test suite in the XLS file now, it will change the name in RQM of the already imported test suite.

0 votes

Comments
Sunil Kumar R
JAZZ DEVELOPER Mar 19 '14, 10:11 a.m.

Hello by point 3. do you mean there are errors pointing to creation of Test Suite? i.e., only Test Case creation goes through successfully and not Test Suite? 


Do you see this behavior with sample sheets in RQM excel exporter?

Best Regards, Sunil

w h
Mar 19 '14, 1:04 p.m.

Point 3 - no errors get thrown, it looks like it creates successfully, but the Test Suite does not get created. 

I also see the same behavior with the sample sheets given, I used:

TestSuite with TestCases 001.cfg and xls

1 answer
3,377 views
0 votes

Accepted answer

Permanent link
Matthieu Leroux
JAZZ DEVELOPER (657●1●6●14) Mar 19 '14, 10:54 a.m.
Hello,

I believe this is an expected behavior, the XLS file name is used for the identifier, you can verify this by viewing the XML for this test suite via the REST API.

the following URL will display all the test suites
https://<server:port>/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/<PROJECT_ALIAS>/testsuite
you can then copy the link location for one of the test suites and use an HTTP client to get the corresponding XML.

Although this seems to be a problem for you, this can work in your advantage if you wanted to rename artifacts that have been created via the Excel importer.

The solution like you pointed already is to rename the XLS file, or to add the test cases to your existing file (downside of this being that every time you import you will process the already imported artifacts)

I hope this helps.
Matthieu
w h selected this answer as the correct answer

1 vote

Comments
w h
Mar 19 '14, 1:07 p.m.

Thanks! I think this will be useful when we have a final XLS ready to import and manage. However as we are still developing the script incrementally, we thought it was an issue with our syntax that was causing the issue. Good to know this info.

Your answer

Register or log in 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.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Mar 19 '14, 9:34 a.m.

Question was seen: 3,377 times

Last updated: Mar 19 '14, 1:07 p.m.

Confirmation Cancel Confirm