http://www.vinktank.com/test-execution/integrating-quick-test-pro-with-cruise-control/ Pragmatic software testing & development by Kristan Vingrys Sat, 04 Sep 2010 16:53:01 +0000 http://wordpress.org/?v=2.2 http://www.vinktank.com/test-execution/integrating-quick-test-pro-with-cruise-control/#comment-855 admin Wed, 04 Feb 2009 10:46:17 +0000 http://www.vinktank.com/test-execution/integrating-quick-test-pro-with-cruise-control/#comment-855 Cruise will call Quality Centre to execute the tests in the test set that you target. The application will need to already be deployed and running, this is normally done as part of the cruise build, after the code has been unit tested and compiled. Cruise will call Quality Centre to execute the tests in the test set that you target. The application will need to already be deployed and running, this is normally done as part of the cruise build, after the code has been unit tested and compiled.

]]> http://www.vinktank.com/test-execution/integrating-quick-test-pro-with-cruise-control/#comment-851 Alexey Tue, 03 Feb 2009 08:40:45 +0000 http://www.vinktank.com/test-execution/integrating-quick-test-pro-with-cruise-control/#comment-851 I don't understand how do you execute tests? Cruise doesn't deploy application to be tested, does it? Thanks I don’t understand how do you execute tests? Cruise doesn’t deploy application to be tested, does it?
Thanks

]]> http://www.vinktank.com/test-execution/integrating-quick-test-pro-with-cruise-control/#comment-354 admin Tue, 13 May 2008 23:23:14 +0000 http://www.vinktank.com/test-execution/integrating-quick-test-pro-with-cruise-control/#comment-354 This should work with either edition of QC, it uses the API to connect to QC which I believe is available for both the starter and Enterprise Editions. There is a better way to do this, I have found tdruntestset.exe to take up a lot of CPU when it is running, I think it sits and polls for the result. I will put up another blog soon about the other way which involves writing your own script that uses the API. This should work with either edition of QC, it uses the API to connect to QC which I believe is available for both the starter and Enterprise Editions. There is a better way to do this, I have found tdruntestset.exe to take up a lot of CPU when it is running, I think it sits and polls for the result. I will put up another blog soon about the other way which involves writing your own script that uses the API.

]]> http://www.vinktank.com/test-execution/integrating-quick-test-pro-with-cruise-control/#comment-353 Ram Tue, 13 May 2008 18:45:22 +0000 http://www.vinktank.com/test-execution/integrating-quick-test-pro-with-cruise-control/#comment-353 hi there- will the starter edition of QC do or do we need the Enterprise edition to make this work? hi there- will the starter edition of QC do or do we need the Enterprise edition to make this work?

]]> http://www.vinktank.com/test-execution/integrating-quick-test-pro-with-cruise-control/#comment-176 Maximus Thu, 20 Dec 2007 07:10:04 +0000 http://www.vinktank.com/test-execution/integrating-quick-test-pro-with-cruise-control/#comment-176 I would like to see a continuation of the topic I would like to see a continuation of the topic

]]> http://www.vinktank.com/test-execution/integrating-quick-test-pro-with-cruise-control/#comment-3 Jeffrey Fredrick Thu, 07 Jun 2007 14:18:19 +0000 http://www.vinktank.com/test-execution/integrating-quick-test-pro-with-cruise-control/#comment-3 Way back when, when I first got involved with CruiseControl, I did something similar run our WinRunner tests under CC, but then went a step further. I wrote a custom Ant task that would read in the contents of the error file and create an XML result file that matched the JUnit format. I'd then have CC merge that into the log and now the WinRunner error messages showed up in the CC email just like the JUnit error message. Was very handy! Way back when, when I first got involved with CruiseControl, I did something similar run our WinRunner tests under CC, but then went a step further. I wrote a custom Ant task that would read in the contents of the error file and create an XML result file that matched the JUnit format. I’d then have CC merge that into the log and now the WinRunner error messages showed up in the CC email just like the JUnit error message. Was very handy!

]]>