Default Report from RPT not sent to RQM.
I have a test case linked to a test schedule in RQM. I ran the TC from RQM, and while the test was running I saw the summary report stats being populated in RQM. When the test ended, in Execution results there is no report i.e.
The verdict is inconclusive because the performance schedule did not have any performance requirements evaluated during the last user stage. Please examine the attached report and set the verdict appropriately. Consider updating the performance schedule to include performance requirements so that the verdict can be set automatically for you based on whether all performance requirements pass or not. No reports available. Any ideas why this is not in RQM, but I do see the report in RPT. |
15 answers
|
For the first test run after starting the adapter, this is the error we were consistently seeing in RQM:
The following message was reported by the adapter engine: Error executing script. Reason: Problems occurred during launch: RPTA4010I An error occurred during code generation. There is no setting associated with the key "variables" Then the next run would execute with no issues. As for the adapter and project workspaces, any shot at getting this functionality as an enhancement request? We are using a 2 license floating structure and it would aid us in an running tests with an enterprise landscape in mind as we take on multiple concurrent projects. Thanks again, Homer When you leave the project area blank, that's telling the adapter to use the default project area (i.e. "Quality Manager"). We allow the project area field to be blank because the adapter is suppose to work with older releases of RQM, were project area wasn't even introduced yet (RQM 1.0). |
I'm not sure what's the deal with the problem you're seeing with the first run. You said you were on RPT 8.1. I think you should move up to a newer release, such as 8.1.1.1, but if you must stay on 8.1 at least move to the latest fixpack. Which is 8.1.0.3.
In terms of 1 RPT adapter working for all RQM project areas at the same time, feel free to submit an RFE. But I can say this isn't trivial to implement. RPT RFEs can be submitted here: http://www.ibm.com/developerworks/support/rational/rfe/ |
|
Hi Kurt,
Going back to this thread to ask a couple of questions. We still seeing an issue where counters are not being gathered. We have an id on the serice that has access to sever which we are gathering stats. but it is different that the credentials specified in the loacation. Is this an issue? We would like this to be generic enough so that when the performance resource leaves (and his/her nt id is decomissioned) stats can still be gathered using our dediated credentials we created specifically for the service. I'm not sure what's the deal with the problem you're seeing with the first run. You said you were on RPT 8.1. I think you should move up to a newer release, such as 8.1.1.1, but if you must stay on 8.1 at least move to the latest fixpack. Which is 8.1.0.3. |
|
These questions are having less to do with the RPT adapter and becoming more specific to RPT's implementation of the resource monitoring component. I'm going to need the help of the RPT team members who work on resource monitoring. Please repost your last question to the RPT forum so I can get the appropriate persons involved:
http://www.ibm.com/developerworks/forums/forum.jspa?forumID=326 Also, there's something not clear about your question. You stated that "We would like this to be generic enough so that when the performance resource leaves (and his/her nt id is decomissioned) stats can still be gathered ...". What do you mean by "the performance resource leaves"? Please clarify that when you post to the RPT forum. Thx. |
|
Will post more details there.
Thanks, Homer These questions are having less to do with the RPT adapter and becoming more specific to RPT's implementation of the resource monitoring component. I'm going to need the help of the RPT team members who work on resource monitoring. Please repost your last question to the RPT forum so I can get the appropriate persons involved: |
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.