Comments for Knowtu http://blog.knowtu.com Do u want to knowTu? Fri, 04 Jul 2008 23:57:21 +0000 http://wordpress.org/?v=2.5 Comment on CruiseControl Custom Listener by Sargon Benjamin http://blog.knowtu.com/2007/10/16/cruisecontrol-custom-listener/#comment-5500 Sargon Benjamin Mon, 12 May 2008 17:13:45 +0000 http://blog.knowtu.com/2007/10/16/cruisecontrol-custom-listener/#comment-5500 Thanks for the quick response. At first glance of your reply, I was a bit confused as to why you had two cruise control instances and which cruisecontrol instance had the custom modification listener. I reread the reply and it makes sense. Thanks for the details. I'll definitely implement something similar for our group upon build completion. We have an fvt framework (it sits on top of HTTPUnit) and I'll have a custom modification listener that waits for a newly published build and then spawns off the test execution script. I'll muck around with seeing what I can do with results and see if I can customize the CC dashboard to include these results. Thank you again! very very helpful Thanks for the quick response. At first glance of your reply, I was a bit confused as to why you had two cruise control instances and which cruisecontrol instance had the custom modification listener. I reread the reply and it makes sense. Thanks for the details. I’ll definitely implement something similar for our group upon build completion. We have an fvt framework (it sits on top of HTTPUnit) and I’ll have a custom modification listener that waits for a newly published build and then spawns off the test execution script. I’ll muck around with seeing what I can do with results and see if I can customize the CC dashboard to include these results.
Thank you again! very very helpful

]]> Comment on CruiseControl Custom Listener by danielh http://blog.knowtu.com/2007/10/16/cruisecontrol-custom-listener/#comment-4806 danielh Mon, 05 May 2008 09:15:27 +0000 http://blog.knowtu.com/2007/10/16/cruisecontrol-custom-listener/#comment-4806 Thanks Sargon, For 1) Yes, we have a nant build script that runs an external script (vbs) (invokes HP winrunner), basically runs installers and runs regression tests. Results are published from winrunner and managed via quality center. If winrunner fails the script fails and fails the cruisecontrol project which of course emails everyone. For 2) The ui tests are on a separate cruise control instance (the one that has the custom modification listener) (separate vm in ESX server), the build, packaging and unit tests happens on a different build machine (it has much more fine grained component projects and an overarching 'publish' and 'nightly-build'). So a publish is really a complete rebuild after doing a fresh get and cleaning (Installshield leaves cruft around) all it then does is (assuming it's successful) copy the built product to a shared build drive on our data store. So if the build fails any earlier due to say unit tests failing it won't get to the installers and the 'publish'. So in that case it won't kick off the ui test on that instance as nothing makes it onto the shared build publish location. So the ui test machine basically watches for a new directory coming in the form of \\share\builds\product\major.minor.patch.build. The whole reason I had to write the custom listener is that the filesystem watcher would be pointed at say \\share\builds\product\ but because often you end up with small file changes when people are installing, using, would trigger too much, so basically we needed a way to ensure that only fresh builds were being picked up. For 3) Results don't really make their way to cruise control (apart from a fundamental fail, and standard nant execution output), they could, we've got another custom tool that we've added in as a separate log consumer, but the results are reported to the testing team who back it up with manual testing. So basically build and unit tests failures get reported to entire dev team, ui CC gets reported to test team + lead dev and ui scripting/fails is managed and reported via the testing management chain. Eg a unit test failing in the dev build wouldn't trigger an incident report, but a regression ui test would get flagged and logged as a bug. Hope this answers your questions, cheers. Thanks Sargon,
For 1) Yes, we have a nant build script that runs an external script (vbs) (invokes HP winrunner), basically runs installers and runs regression tests. Results are published from winrunner and managed via quality center. If winrunner fails the script fails and fails the cruisecontrol project which of course emails everyone.
For 2) The ui tests are on a separate cruise control instance (the one that has the custom modification listener) (separate vm in ESX server), the build, packaging and unit tests happens on a different build machine (it has much more fine grained component projects and an overarching ‘publish’ and ‘nightly-build’). So a publish is really a complete rebuild after doing a fresh get and cleaning (Installshield leaves cruft around) all it then does is (assuming it’s successful) copy the built product to a shared build drive on our data store. So if the build fails any earlier due to say unit tests failing it won’t get to the installers and the ‘publish’. So in that case it won’t kick off the ui test on that instance as nothing makes it onto the shared build publish location. So the ui test machine basically watches for a new directory coming in the form of \\share\builds\product\major.minor.patch.build. The whole reason I had to write the custom listener is that the filesystem watcher would be pointed at say \\share\builds\product\ but because often you end up with small file changes when people are installing, using, would trigger too much, so basically we needed a way to ensure that only fresh builds were being picked up.
For 3) Results don’t really make their way to cruise control (apart from a fundamental fail, and standard nant execution output), they could, we’ve got another custom tool that we’ve added in as a separate log consumer, but the results are reported to the testing team who back it up with manual testing. So basically build and unit tests failures get reported to entire dev team, ui CC gets reported to test team + lead dev and ui scripting/fails is managed and reported via the testing management chain. Eg a unit test failing in the dev build wouldn’t trigger an incident report, but a regression ui test would get flagged and logged as a bug.

Hope this answers your questions, cheers.

]]> Comment on CruiseControl Custom Listener by Sargon Benjamin http://blog.knowtu.com/2007/10/16/cruisecontrol-custom-listener/#comment-4426 Sargon Benjamin Fri, 02 May 2008 08:47:31 +0000 http://blog.knowtu.com/2007/10/16/cruisecontrol-custom-listener/#comment-4426 Awesome post! A couple questions for ya if you have the time.. 1. What happens once your custom filesystem modificationset detects that a new build has been published? And how do you respond to a notification? (ie, once you know that a new build has been published, how do you then call your remote UI tests? Do you have code in your plugin that calls an external script to do this?) 2. What happens when you have a build failure? My guess is that the filesystem modificationset will think there's a new build available and then start the UI test execution process. How do you tell the filesystem modificationset plugin not to execute your FVT tests if the build has failed? 3. How do you report the results of your UI test cases and do these results make their way back to CruiseControl? - Thank you kindly Sargon Awesome post! A couple questions for ya if you have the time..
1. What happens once your custom filesystem modificationset detects that a new build has been published? And how do you respond to a notification? (ie, once you know that a new build has been published, how do you then call your remote UI tests? Do you have code in your plugin that calls an external script to do this?)

2. What happens when you have a build failure? My guess is that the filesystem modificationset will think there’s a new build available and then start the UI test execution process. How do you tell the filesystem modificationset plugin not to execute your FVT tests if the build has failed?

3. How do you report the results of your UI test cases and do these results make their way back to CruiseControl?

- Thank you kindly
Sargon

]]> Comment on WordPress Theming by Zepleoxiplike http://blog.knowtu.com/2007/10/16/wordpress-theming/#comment-62 Zepleoxiplike Thu, 07 Feb 2008 09:08:38 +0000 http://blog.knowtu.com/2007/10/16/wordpress-theming/#comment-62 Nice site keep it up! http://www.dasofte.com Nice site keep it up!

http://www.dasofte.com

]]> Comment on Good Code, Bad Things by Bad Debt » Blog Archive » Good Code, Bad Things http://blog.knowtu.com/2008/02/02/good-code-bad-things/#comment-61 Bad Debt » Blog Archive » Good Code, Bad Things Sun, 03 Feb 2008 03:19:54 +0000 http://blog.knowtu.com/2008/02/02/good-code-bad-things/#comment-61 [...] Read the rest of this great post here [...] […] Read the rest of this great post here […]

]]> Comment on Good Code, Bad Things by Tim Ramsey http://blog.knowtu.com/2008/02/02/good-code-bad-things/#comment-60 Tim Ramsey Sun, 03 Feb 2008 02:54:33 +0000 http://blog.knowtu.com/2008/02/02/good-code-bad-things/#comment-60 I found your site on technorati and read a few of your other posts. Keep up the good work. I just added your RSS feed to my Google News Reader. Looking forward to reading more from you. Tim Ramsey I found your site on technorati and read a few of your other posts. Keep up the good work. I just added your RSS feed to my Google News Reader. Looking forward to reading more from you.

Tim Ramsey

]]> Comment on CruiseControl Custom Listener by celpjefscycle http://blog.knowtu.com/2007/10/16/cruisecontrol-custom-listener/#comment-59 celpjefscycle Sat, 12 Jan 2008 09:42:49 +0000 http://blog.knowtu.com/2007/10/16/cruisecontrol-custom-listener/#comment-59 Thanks for information. many interesting things Celpjefscylc Thanks for information.
many interesting things
Celpjefscylc

]]> Comment on WordPress Theming by Melina http://blog.knowtu.com/2007/10/16/wordpress-theming/#comment-36 Melina Fri, 21 Dec 2007 04:48:41 +0000 http://blog.knowtu.com/2007/10/16/wordpress-theming/#comment-36 very interesting. i'm adding in RSS Reader very interesting. i’m adding in RSS Reader

]]> Comment on Resharper + IDEA by Slow Cooking » Resharper + IDEA http://blog.knowtu.com/2007/11/01/resharper-idea/#comment-4 Slow Cooking » Resharper + IDEA Fri, 02 Nov 2007 07:17:05 +0000 http://blog.knowtu.com/2007/11/01/resharper-idea/#comment-4 [...] Knowtu wrote an interesting post today on Resharper + IDEAHere’s a quick excerpt One of the things I picked up in my last job (pure J2EE/Swing) was Jetbrains IntelliJ IDEA … always been a little flaky, slow and suffer a bit from multiple personality disorder. The one thing … gained slow adoption to about 75% of the team. One really good thing about the philosophy here [...] […] Knowtu wrote an interesting post today on Resharper + IDEAHere’s a quick excerpt One of the things I picked up in my last job (pure J2EE/Swing) was Jetbrains IntelliJ IDEA … always been a little flaky, slow and suffer a bit from multiple personality disorder. The one thing … gained slow adoption to about 75% of the team. One really good thing about the philosophy here […]

]]> Comment on WordPress Theming by retro http://blog.knowtu.com/2007/10/16/wordpress-theming/#comment-3 retro Thu, 01 Nov 2007 14:58:27 +0000 http://blog.knowtu.com/2007/10/16/wordpress-theming/#comment-3 I do love the classics. I do love the classics.

]]>