It's all about the answers!

Ask a question

Access Custom RQM Testplan Section in JRS


Thomas Kirstätter (181415) | asked Aug 28 '17, 11:41 a.m.
edited Sep 25 '17, 7:49 a.m.

Hello,
our situation is:
We used a custom attribute in RQM with size medium text to capture some data we need for our quality process and used JRS to report on it.
Unfortunately, the size of the information we needed to store exceeded the amount that fits into a medium text attribute.

We now did create a custom section in the TestPlan template (rich text) in which our data fits but it seems this is not accessible in JRS (neither DWH nor LQE).
Is there any option we have to solve our issue?

Solution of cause could be as well to increasing the amount of data that can be stored in an medium text attribute.



I already found these questions related to RPE:
https://jazz.net/forum/questions/89659/print-custom-section-in-rqm-using-rpe
https://jazz.net/forum/questions/124705/how-to-query-custom-rqm-test-suite-section-with-rpe 


Edit:
I found that when using LQE, there is an option in the tractability section of the Report builder to access a "Rich Text Section" could this be used? LQE would of cause be absolutely possible as a solution if DWH doesn't offer this data...

Edit 2017-09-25:
We tried to access our custom Rich text Section via LQE (using JRS Report Builder). Can anyone please comment if this should work w.r.t the design? I can see all the system defined Rich text Sections if they are used in a Test Plan, but not our Custom one.

2 answers



permanent link
Thomas Kirstätter (181415) | answered Mar 02 '18, 3:10 p.m.

There is an fix included in RQM 6.0.4 iFix005 (I think) that now allows custom rich text sections to be accessed with REST API and as well published to LQE. Thus it can now be reported normally.

Many thanks to the RQM Dev Team!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


permanent link
Kenji Sarai (96029) | answered Aug 28 '17, 10:28 p.m.

Hi Thomas,

The two links you referred to are about the qm.xsd data source schema used in RPE, which explain the workaround of defect as below
http://www-01.ibm.com/support/docview.wss?uid=swg1PI65792

The problem in JRS is where to accommodate the custom attribute ( rich text ) in data warehouse. The following is the list of data stored in data warehouse.
https://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.4/com.ibm.rational.test.qm.doc/topics/qm/Test-Plan.html

Medium text attributes are stored in table RICALM.TESTPLAN_STRING_M_EXT, but I am not sure which table for rich text attribute (RICALM.TESTPLAN_STRING_EXT ?). Can you find any data by SQL query (advanced section) as below?

select * from RICALM.TESTPLAN_STRING_EXT

or try using other tables listed in the link as above.


Comments
Thomas Kirstätter commented Aug 29 '17, 2:01 a.m.

Hi Kenji,

Thanks for the hints above.
As far as I found out, the data of sections is stored differently. e.g. there is a section called "Quality Objectives" which is in the JRS reportbuilder available via setting a Traceability link. (Testplan -- all link types--> Quality Objectives. And in the datadictionary you provided, it is in a explicit table TESTPLAN_OBJECTIVESTATUS. Until now I could not find a trace, but I did as well not yet check all information in the datadictionary, buts already many thanks!!!!!!!!


Kenji Sarai commented Aug 31 '17, 1:56 a.m.

Quality objectives can be linked with Testplans and also reportable.
https://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.4/com.ibm.rational.test.qm.doc/topics/t_quality_obj_scenario.html

If you find where the custom attribute ( rich text ) is stored in data warehouse, please update here. 


1
Thomas Kirstätter commented Aug 31 '17, 3:09 p.m.

Hi Kenji,
my status: These informations besides the Quality Objectives cannot be accessed via Datawarehouse. The solution at the moment is only possible in LQE:
Build a Report based on LQE as source -> Select QM Testplan as artefact -> In the Traceability option, you can now select a Link to "Rich Text Section". The Rich Text Section Object has a Title, a Description, Content... The Title is the name of the Section, The Description is the description from the section definition and the Content is the actual rich text field. You can define conditions for the attributes of the Rich text Sections and show them in the result table.
I am still in the process of testing with my specific custom section, but currently it seems this is the only option...

Your answer


Register or to post your answer.