Running multiple RQM Command Line Adapters
Philipp Hoffmann (8●1●2●4)
| asked Mar 06 '14, 5:57 a.m.
edited Mar 07 '14, 6:12 p.m. by Max Bridges (241●2●6)
Our team is using a build process based on RTC and we have created a scheduled job in RQM that executes automated tests (using the CLA) based on the successful completion of a certain build definition.
This works fine for our current release. However we have multiple build definitions (for different releases) and many need to be tested using RQM and the CLA. The actual test is pretty similar for across all these releases, so that passing a different property from RQM to the CLA here and there should be sufficient to configure what needs to be done. I'd appreciate some clarification regarding the following questions:
|
Accepted answer
There are some configuration settings for RQM to choose which adapter to run. Take a look at this link and see if this is what you are looking for under "Specifying that a suitable..."
You can allocate an adapter to execute automated tests by doing one of these things:
This will allow RQM to pick any available one. Philipp Hoffmann selected this answer as the correct answer
|
One other answer
Hi Philipp,
I'm not sure I understand the question about version: There is one CLA per RQM version. You copy the file <server_root>/server/conf/qm/adapters/RQMCommandLineAdapter.zip to the
System Under Test (SUT). You can do this on multiple machines, and thus can run tests in parallel.
You initiate a connection from each to a particular RQM server and project area (and it can be the same one).
In the RQM Adapter Console Menu, you can see a list of all the adapters and their current status/Health.
So its the same adapter, but unzipped and installed on several machines.
What do you mean about creating different ones?
Toni
Comments
Philipp Hoffmann
commented Mar 07 '14, 1:56 a.m.
Hi Toni,
|
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.