At work we have started a KanBan board. We needed to put post-its with tasks on there.
My name disappeared under the post-its! I have been literally buried by tasks.
However, have a brief moment to look at my e-mail and see lots of queries about my integration.
Indeed we have successfully made this integration.
It works OK, but we are not really satisfied with the resulting situation.
The issues I am aware of with making a direct integration from VAPI-XP-TEST:
* Version dependencies between Python and Quality Center.
* We used COM, but HP is moving towards REST. At the time we started (QC version 11), OTA did not support all functionality we needed.
* Running larger sets of tests is cumbersome. Robot Framework has a nice way of handling Suite setup for a whole suite - Quality Center is not so useful in this regard.
* For integration with a Continuous Integration server, Quality Center is a hinderance. It is not impossible (there are integrations with Jenkins for example), but it is also not always helpful.
* It turns out that storing lots of configuration data in Quality Center is not the desired approach. Quality Center is a Test management tool - the test execution and associated data needs to be elsewhere.
A better approach is to develop all tests and data management with Robot Framework directly.
Run Robot Framework independently.
Use a proper version control system to store the test sets (Quality Center is not so good at version controlling sets of information).
Synchronise the results back into Quality Center. I have not yet decided how to associate the test in Robot Framework with the test in Quality Center - maybe some clever use of Tags can be used?
For us, this would be the next phase of evolution of our solution. However, we are in the middle of a major merger so all such developments are on-hold for now.
I would be keen to know other thoughts on this - maybe between us we can think of something even better.