I was glad to read that Roy Osherove is re-gathering the Agile-Israel group after a year or so with no meetings. Next meeting is this week, but unfortunately the last week of August is the the longest weekend ever for us preschool-parents, so no soup for me until next time...
http://weblogs.asp.net/rosherove/archive/2007/08/20/be-sure-to-register-for-agile-israel-august-meeting.aspx
Monday, August 27, 2007
Selenium and CruiseControl
Surprisingly, running Selenium tests under CruiseControl seems to be one of the least-covered topics in the agile community.. After going through the few articles on the matter (a pretty good one here and a not so promising one on the CruiseControl wiki here) I decided to roll my own.
It seems that most solutions (well, I only found two so "most" might be a harsh word here :-) require some knowledge of NAnt (which I lack) and incorporate lot's of temporary files, logs, xsl-transformations, server scripts and other such cuss-words which all make me feel a bit sea-sick.
I prefer to keep things encapsulated and clean, so my idea was to make a simple task (say a command-line EXE that can be run through a simple CruiseControl <exec> task). This task would open up some kind of in-process HTTP-listener waiting for the Selenium results to come in, and then run the Selenium TestRunner in a browser, telling it to report back to our listener when it's done. Once the results come in - we just need to analyze them, return some Cruise-Control-friendly result code and close the browser. Simple, right?
Well in fact it *was* that simple, and worked like a charm! The highlight was using DotNet 2.0's HttpListener class with help from Rick Strahl's excellent wrapper posted here. The code is still all too spiky to show it's face in public, but I'll be sure to post it soon, so stay tuned!
It seems that most solutions (well, I only found two so "most" might be a harsh word here :-) require some knowledge of NAnt (which I lack) and incorporate lot's of temporary files, logs, xsl-transformations, server scripts and other such cuss-words which all make me feel a bit sea-sick.
I prefer to keep things encapsulated and clean, so my idea was to make a simple task (say a command-line EXE that can be run through a simple CruiseControl <exec> task). This task would open up some kind of in-process HTTP-listener waiting for the Selenium results to come in, and then run the Selenium TestRunner in a browser, telling it to report back to our listener when it's done. Once the results come in - we just need to analyze them, return some Cruise-Control-friendly result code and close the browser. Simple, right?
Well in fact it *was* that simple, and worked like a charm! The highlight was using DotNet 2.0's HttpListener class with help from Rick Strahl's excellent wrapper posted here. The code is still all too spiky to show it's face in public, but I'll be sure to post it soon, so stay tuned!
Sunday, August 26, 2007
I am lazy therefore I am
OK, so the balloon has popped.
Over the last several days I've been trying to write down some brilliant posts about the best subjects ever, just to realize It's not all fun and games - so here it is. A short realization of one's self. I am lazy, lazy am I.
Ahh.. Much better now. I bet the next post shall be really brilliant. Oh yes, it shall.
Over the last several days I've been trying to write down some brilliant posts about the best subjects ever, just to realize It's not all fun and games - so here it is. A short realization of one's self. I am lazy, lazy am I.
Ahh.. Much better now. I bet the next post shall be really brilliant. Oh yes, it shall.
Monday, August 20, 2007
Hello World!
Ummm... Hello world?
So you've guessed it - this is my first dip into the blog'o-puddle.
For some time now I've been pondering about a blog, and I guess pondering time is over - so here goes..
Why, oh why another blog?
One of my goals for this blog is as a Professional Development tool.
I've been learning and implementing new ideas throughout my professional life, learning as I go and trying to get myself ahead one step at a time. For the past several years my main learning subject was Agile development in general and Test-Driven Development in particular.
Although I've been able to learn and even incorporate these methodologies in my work, after reading this article by Andy Warren about professional development I realized something was missing - a greater plan, a defined goal. So under the influence it all came together in a flash of white light - "A blog! I need a blog! I MUST have a blog!!!". Yes, it seems like posting my rants and ideas on a blog might not only make a good outlet for my sleepless idea-infested mind, but might even commit me into molding my learning path into something more useful, if not to myself then at least to others (or was that the other way around?)
If you're reading this, you're too close
...Or maybe I'm too naive. Either way it'll be interesting to see what feedback I get from this blog apart from my own..
Agile Shmagile
Yes, I know it's probably the most over-hyped subject these days, nevertheless Agile and Test Driven Development will probably be the main subject-matter for this blog simply because.. umm.. well because I say so :-)
Enough is enough
So enough ranting for now, let's get this iteration wrapped up.
Hit F5, "Hello World" tests all green, release time!
So you've guessed it - this is my first dip into the blog'o-puddle.
For some time now I've been pondering about a blog, and I guess pondering time is over - so here goes..
Why, oh why another blog?
One of my goals for this blog is as a Professional Development tool.
I've been learning and implementing new ideas throughout my professional life, learning as I go and trying to get myself ahead one step at a time. For the past several years my main learning subject was Agile development in general and Test-Driven Development in particular.
Although I've been able to learn and even incorporate these methodologies in my work, after reading this article by Andy Warren about professional development I realized something was missing - a greater plan, a defined goal. So under the influence it all came together in a flash of white light - "A blog! I need a blog! I MUST have a blog!!!". Yes, it seems like posting my rants and ideas on a blog might not only make a good outlet for my sleepless idea-infested mind, but might even commit me into molding my learning path into something more useful, if not to myself then at least to others (or was that the other way around?)
If you're reading this, you're too close
...Or maybe I'm too naive. Either way it'll be interesting to see what feedback I get from this blog apart from my own..
Agile Shmagile
Yes, I know it's probably the most over-hyped subject these days, nevertheless Agile and Test Driven Development will probably be the main subject-matter for this blog simply because.. umm.. well because I say so :-)
Enough is enough
So enough ranting for now, let's get this iteration wrapped up.
Hit F5, "Hello World" tests all green, release time!
Subscribe to:
Posts (Atom)