How to use test cells with execution schedules if machines will be chosen at runtime? We always getting the message "Internal Error".
Hi together,
We are using RQM 4.0.7 and want to use test cells in execution schedules as follows: 1. The test cell contains Lab Resources matching the test environment "EnvA" resource descriptions. => Lab Resource Descriptions for Test Envionment "Env A"2. The test suite execution record (TSER) is assigned to a test environment "EnvB" which specifies a superset of resources specified by EnvA. => Lab Resource Descriptions for Test Envionment "Env B"For selecting the right machine only the first attribute "UDS" is relevant, therefore the test cell maps only to that attribute. 3. An Execution Schedule (ES) with this test cell specified, all needed TSERs as steps and all machines configured to be chosen at runtime Now, when we run this Execution Schedule, the error message is "Internal Error" - nothing more specific. We see the TSER not attempted so suspect the problem to be related to the calling instance. The problem does not occur when we explicitly specify the machine to run with, so selecting the machine in advance. But that does not help in dynamically allocating resources! Many thanks in advance! |
One answer
Hi Stefan,
Do you see any exceptions in qm.log file. Do you see the same error when running the TSER manually? Comments
Stefan Abraham
commented Jan 08 '16, 11:21 a.m.
Hi Reshma, where can I find the qm.log file?
Kevin Ramer
commented Jan 08 '16, 2:12 p.m.
The log file will be on the QM server, but could be anywhere. One would need to check the server/conf/qm/log4j.properties.
File Appender - Threshold WARNThe File attribute represents the log file name and location
|
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.
Comments
There is something familiar here; let me research my support requests.
One thing I am remembering in this context. It had to do with the lab resources being owned by different project area and some users had no visibility to that project.