It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×11,924
×10,908

question asked: Sep 24 '13, 4:12 a.m.
question was seen: 5,739 times
last updated: Feb 02 '15, 8:19 a.m.

Related questions

FAQ - How this Forum works

How to use the RQM Execution Tool to run a test suite execution record ?

1
FREDERIC HENOUILLE (21●1●1) | asked Sep 24 '13, 4:12 a.m.
Hello,

We launch a test suite with the RQMExecutionTool:

The following command launches the testsuite but the execution does not progress :

C:\RQMExeTool>"C:\Program Files\Java\jre1.6.0_06\bin\java.exe" -jar RQMExecutionTool.jar -tserId=5019 -projectName="PTV" -publicURI=https://wpmmi135.ressources.racine.local/qm  -user=e142 -password=e142 -exitOnComplete=true


The following command works, but we have to specify all the test scripts of the test suite (more than 50 testscripts) :

C:\RQMExeTool>"C:\Program Files\Java\jre1.6.0_06\bin\java.exe" -jar RQMExecutionTool.jar -tserId=5019 -projectName="PTV" -publicURI=https://wpmmi135.ressources.racine.local/qm  -user=e142 -password=e142 -suiteStepScriptIds=2166 -exitOnComplete=true -adapterId=74


Any help would be greatly appreciated

  Frederic


Details :

C:\RQMExeTool>"C:\Program Files\Java\jre1.6.0_06\bin\java.exe" -jar RQMExecutionTool.jar -tserId=5019 -projectName="PTV" -publicURI=https://wpmmi135.ressources.racine.local/qm  -user=e142 -password=e1
42 -exitOnComplete=true -adapterId=74
java.security.NoSuchAlgorithmException: SSL_TLS SSLContext not available
Unable to create SSL_TLS context, trying TLS
23 sept. 2013 18:19:11 com.ibm.rqm.executiontool.util.ExecutionLogger logInfo
INFO: Successfully created an HTTP client
java.security.NoSuchAlgorithmException: SSL_TLS SSLContext not available
Unable to create SSL_TLS context, trying TLS
23 sept. 2013 18:19:11 org.apache.commons.httpclient.HttpMethodDirector isRedirectNeeded
INFO: Redirect requested but followRedirects is disabled
23 sept. 2013 18:19:11 com.ibm.rqm.executiontool.util.ExecutionLogger logInfo
INFO: Connection to RQM Server is established
23 sept. 2013 18:19:11 com.ibm.rqm.executiontool.util.ExecutionLogger logInfo
INFO: Starting TestSuite Execution
23 sept. 2013 18:19:12 com.ibm.rqm.executiontool.util.ExecutionLogger logInfo
INFO: Execution instance created on server with Test Suite Log Id 24985
23 sept. 2013 18:19:12 com.ibm.rqm.executiontool.util.ExecutionLogger logInfo
INFO: Testsuite Execution started
23 sept. 2013 18:19:12 com.ibm.rqm.executiontool.util.ExecutionLogger logInfo
INFO: Execution is in proress:
23 sept. 2013 18:19:22 com.ibm.rqm.executiontool.util.ExecutionLogger logInfo
INFO: Execution is in proress:
23 sept. 2013 18:19:32 com.ibm.rqm.executiontool.util.ExecutionLogger logInfo
INFO: Execution is in proress:
23 sept. 2013 18:19:43 com.ibm.rqm.executiontool.util.ExecutionLogger logInfo

2 answers

Most liked answers ↓|Newest answers|Oldest answers

0
permanent link
Andrey Dodonov (6) | answered Feb 02 '15, 8:19 a.m. 
It seems that regardless of what you use - simple command line (batch file) or ant script, you can not specify the adapterId for the whole test suite execution record, this parameter is valid only for test case execution record. So it is really frustrating, especially if you have number of tests 10+. It is crazy to write -suiteStepAdapterIds=30,30,30,30,... (as many times as many tests you have). They should have allowed -adapterId option for test suite as well. And then may be something like -suiteStepAdapterIds=1_35,17_36 to partially overwrite adapterId if necessary, where the first number is test number and the second number after "_" is adapterId.
0
permanent link
Rasmita Mahapatra (91●1) | answered Sep 25 '13, 12:20 a.m.
JAZZ DEVELOPER
This is the way the suiteStepScriptIds and suiteStepAdapterIds needs to be specified. I can see you are using "adapterId". Please go through this link below, which will help you to specify the parameters properly.

https://jazz.net/wiki/bin/view/Main/RQMExecutionTool#RQM_Execution_ANT_tasks

suiteStepScriptIds Optional comma-separated script IDs for each step in order. Leave this attribute blank for a step where not applicable or want to use default script. For instance, to specify scriptId4 for step 1 and script 78 for step 3 for a suite with five steps, the argument value is 4,,78,, No
suiteStepAdapterIds Optional comma-seperated adapter IDs or names for each step in the order of step. Leave this attribute blank for a step where adapter is not required or want RQM to assign an adapter. For instance, to specify adapterId 20 for step 2 and 15 for step 3 for a suite with three steps, the argument value is ,20,15

Your answer

Register or to post 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.