REST API error for call in ALM 11.0

Question ID: 105650
2
0

Having read the REST API help file, it shows examples for retrieving test cases based on requirement ID coverage.

Here is an example call that we are trying:
http://myserver:8080/qcbin/rest/domains/DEFAULT/projects/LOGAN/tests?login-form-required=y&query={requirement.id[1278]}

Now requirement ID1278 is a valid and is the LOGAN project. In the UI you can open it, view the tests that cover it, etc.
When attempting the above call directly in IE window, I get an XML error:

qccore.general-error
Failed to obtain filter for table ‘TEST’
com.mercury.optane.core.CTdException: The relation from requirement to test is not
defined in the project at
com.mercury.td.tdserver.tdutil.filter.xfilter.XFilterFactory.getRelationForFilter(XFilterFactory.java:450) at
com.mercury.td.tdserver.tdutil.filter.xfilter.XFilterFactory.generateNewFilter(XFilterFactory.java:381) at
com.mercury.td.tdserver.tdutil.filter.xfilter.XFilterFactory.createXFilter(XFilterFactory.java:347) at
com.mercury.td.tdserver.tdutil.filter.CFilter$CFilterRecord.(CFilter.java:205) at
com.mercury.td.tdserver.tdutil.filter.CFilter.createFilterRecord(CFilter.java:145) at
com.mercury.td.tdserver.tdutil.filter.CFilter.frecToFilterRecord(CFilter.java:156) at
com.mercury.optane.core.db.filter.DBFilter.loadFromString(DBFilter.java:193) at
com.mercury.td.tdserver.tdutil.filter.CFilter.loadFromString(CFilter.java:168) at
com.mercury.td.tdserver.tdutil.filter.CFilterFactory.getFilter(CFilterFactory.java:88) wrapped in
com.mercury.optane.core.CTdException: Failed to obtain filter for table ‘TEST’ at
com.mercury.td.tdserver.tdutil.filter.CFilterFactory.getFilter(CFilterFactory.java:91)

Other REST API commands seem to work, and some of the XML retuned seems to show some action, but unsure of why I get an error.

ALM 11.0 patch 14 is what my server is currently on.

Marked as spam
Posted by (Questions: 26, Answers: 22)
Asked on October 24, 2014 9:29 pm
9 views
Answers (1)
2
Private answer

Hello,

Known issue by HP and already fixed.

The fix is part of updates covered in patch 18:

QCCR1J69684 Via REST API, it was possible to get the requirements filtered by the covering test IDs but not the tests filtered by the covered requirements. For example: /requirements?query={test.id[184]} worked but /tests?query={requirement.id[456]} did not work.

Please go about upgrading to patch 18 in order for your REST API command to pull proper results. I have tested out your same line (changing domain, project and the req ID number) and had success under patch 18.

Marked as spam
Posted by (Questions: 1, Answers: 116)
Answered on October 24, 2014 9:32 pm
Thanks, that QCCR does seem to cover it. I will get about patching then.
( at October 24, 2014 9:46 pm)