Unable to get the cancelled task status from RQM using Automation Adapter
We have an Automation adapter with RQM 4.0.3 and OSLC REST API 2.0 specification.
we are facing issue while stopping the execution of RQM test case using the "Stop Run" option on Test Case execution window.
Adapter is not able to get the status of the cancelled task from RQM.
We referred the following docs for our references:
https://jazz.net/wiki/bin/view/Main/RQMTestAutomationAdapterAPI
Any pointers regarding this issue is highly appreciated.
Thanks & Regards,
Pankaj Mishra
we are facing issue while stopping the execution of RQM test case using the "Stop Run" option on Test Case execution window.
Adapter is not able to get the status of the cancelled task from RQM.
We referred the following docs for our references:
https://jazz.net/wiki/bin/view/Main/RQMTestAutomationAdapterAPI
Any pointers regarding this issue is highly appreciated.
Thanks & Regards,
Pankaj Mishra
2 answers
Hi Pankaj,
I suggest you run a similar automated execution with the out-of-the-box Command Line Adapter and test the "Stop Run". If that is working in the similar environment, then you at least know to focus on your customized Adapter code.
The applicable note I see referenced here for developing one is this:
27. Now adapter needs to fork a separate thread for execution. Note that it is important to fork another thread which can be stopped if execution has been canceled in Rational Quality manager.
The applicable note I see referenced here for developing one is this:
27. Now adapter needs to fork a separate thread for execution. Note that it is important to fork another thread which can be stopped if execution has been canceled in Rational Quality manager.
Pankaj,
I'm not sure if this will help, but you could try turning up the adapter logging level. This will generate *a lot* of output, so you would only want to turn it on for sparingly, but it may help debug this. In the log4j.properties file for the adapter, add:
Toni
I'm not sure if this will help, but you could try turning up the adapter logging level. This will generate *a lot* of output, so you would only want to turn it on for sparingly, but it may help debug this. In the log4j.properties file for the adapter, add:
log4j.logger.com.ibm.rqm.adapter.library=DEBUG
log4j.logger.com.ibm.rqm.adapter.commandline=DEBUG
# added for execution
log4j.logger.com.ibm.rqm.integration.client.clientlib=DEBUG
log4j.logger.com.ibm.rqm.execution=DEBUG
Restart the adapter.
To stop this extra logging, remove these lines and restart the adapter.
Restart the adapter.
To stop this extra logging, remove these lines and restart the adapter.
Toni