Custom test harness with RQM?
We use custom test drivers and harnesses for automated test execution on each of the components in our products. Is this something we can integrate with RQM? We don't mind if it means extending and using the API for posting results, I just have not been able to find a topic which covers it.
Most of our testing is command line driven for ease of execution. and we have control over the result output(currently an internal standard xml)
has anyone set up in this type of scenario?
Most of our testing is command line driven for ease of execution. and we have control over the result output(currently an internal standard xml)
has anyone set up in this type of scenario?
2 answers
wolfeb99 wrote:
for it to execute command line scripts. If you have your results go to
stdout then it is easy to capture the results in RQM.
We use custom test drivers and harnesses for automated test execution
on each of the components in our products. Is this something we can
integrate with RQM? We don't mind if it means extending and using
the API for posting results, I just have not been able to find a
topic which covers it.
Most of our testing is command line driven for ease of execution. and
we have control over the result output(currently an internal standard
xml)
has anyone set up in this type of scenario?
I think the command line adapter would work for you. It is very easy
for it to execute command line scripts. If you have your results go to
stdout then it is easy to capture the results in RQM.
We use custom test drivers and harnesses for automated test execution on each of the components in our products. Is this something we can integrate with RQM? We don't mind if it means extending and using the API for posting results, I just have not been able to find a topic which covers it.
Most of our testing is command line driven for ease of execution. and we have control over the result output(currently an internal standard xml)
has anyone set up in this type of scenario?
RQM provides a command-line script type. You can deploy the command-line adapter to your test driver machines. Create command-line scripts to execute your proprietary scripts. Whatever those scripts write to stdout, will be attached to the script details section of the execution results.