Unitils provides its own DataSource. This causes problems if you want to use Spring IOC to inject your own. There is a way around this but its not elegant. In future versions of unitils I believe the team is going to provide better support for less intrusive methods. This post documents a way to use your own spring defined DataSource.
Continue reading
I was talking to Shay Banon (Gigaspace Software Architect) he mentioned using GigaSpaceFactoryBean for writing gigaspace unit tests. I could find no examples on their site, although I concede it may be there somewhere. This shows post shows a simple example.
He also mentioned using the admin api to do full end to end integration testing. The admin api has huge potential as its able to control gigaspace containers, deploy into them and collect statistics. Its a powerful api.
This is documented on their site: http://www.gigaspaces.com/wiki/display/XAP7/Administration+and+Monitoring+API
Continue reading
On the 18th of May, 2010, the very new tumbler-glass project by Studio Pragmatists uploaded Tumbler 0.2.1 to Maven. Having recently written about JBehave I found myself really liking the concept of behavior driven development. So I decided to write a similar article about Tumbler. If you want the project code its available in my example project.
Once again I decided to time box the work to 4 hours. This time though the whole process only took about 20 minutes. The product owner and testers produce a story file. The Tumbler format allows for multiple stories each containing scenarios, so its possible to cover a complex set of requirements in one file. This allows for flexibility when breaking down the work into tasks. As per the usual behavior driven approach, a scenario contains the Given, When and Then sections which describe the behavior. Continue reading
I wanted to explore the possibility of using JBehave to formalise scrums definition of done. The idea being to encapsulate a definition of done as a JBehave scenario. So in true scrum style I decided to timebox 4 hours of work dedicated to JBehave.
From a scrum point of view BDD can be used to turn the definition of done into a test artifact. The team produces scenarios for each task. With JBehave a scenario file describes the required behavior and test steps it will need to pass to be considered done. I.e Given some prerequisites, perform some action and expect some results. See the JBehave project for more detail as this is only a simple example. Continue reading