tag:blogger.com,1999:blog-79298902011-04-21T18:20:19.917-05:00Jim Bethancourthttp://www.blogger.com/profile/12379393665149627069noreply@blogger.comBlogger11100tag:blogger.com,1999:blog-7929890.post-43189072230326175432007-11-05T23:05:00.000-06:002007-11-05T23:26:25.550-06:00I had the opportunity a few weeks ago to try out <a href="http://gojko.net/fitnesse/dbfit/">dbFit</a>, a <a href="http://fitnesse.org/">FitNesse</a> fixture after reading about it on <a href="http://www.infoq.com/news/2007/03/dbfit">InfoQ</a>. We were unit testing our stored procedures in our database, and dbFit was a great "fit". It took me a while to get going because I hadn't worked with FitNesse before, so in essence I was learning two technologies at once. Once I figured it out, though, it was a real pleasure to work with, and Gojko was very helpful in fixing a bug and adding an Update command that I had suggested.<br /><br />A few helpful practices I figured out along the way:<br />- Declare your classpath in your test suite page<br />- Have your database connection declared in your SetUp page for your suite<br />- Have links to your tests from your suite page so you can get to them without having to run your test suite<br /><br />We're going to have John Tyler talk more about FitNesse at the next HJUG meeting on January 30th, and I'm definitely looking forward to it. Gojko's work makes me wonder if I could try and write a JPA / EJB3 FitNesse fixture... It would be quite an undertaking, but I think it could be very useful.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7929890-4318907223032617543?l=jimbethancourt.blogspot.com' alt='' /></div>Jim Bethancourthttp://www.blogger.com/profile/12379393665149627069noreply@blogger.com0