In a previous blog on TDD I advocated that you should define your test on a high level. One of the reasons why you should use a high level language is that you can use your tests not only for your API but also for for instance your UI. In this blog I will show how you can use the same test pages in FitNesse to test both the API and UI of your system.
|
||||||
|
I am practicing TDD for some years now and it took me a while and some mistakes to fully take advantage of it. Unfortunately I see a lot of people struggling with TDD and making the same mistakes I have made in the past. So here is a summary of what I think are the key aspects of TDD: Sometimes when I start a project I already have some folder structure and code in place that I want to put into Subversion. However there are also already some files and folders present that I want to ignore on import. Subversion does not provide a way to ignore files on svn:import using the command line. But by using the global-ignores feature you can ignore files on svn:import when you follow these steps. Recently I found out about Springs ClassPathScanningCandidateComponentProvider. This class allows you to scan the classpath from a base package at runtime. This is extremely handy in all kind of situations, for instances in testing. Yak shaving can lead to useless work, but sometimes it can lead to very interesting facts… like finding out where Kaizen comes from. Hibernate’s SessionFactory has some very powerful functions available like generating your tables from your hbm files using the hbm2ddl.auto property. This is very handy for laptop testing where you can let hibernate generate your complete scheme on the fly. Continue reading Generating sql files in Maven using hibernate tools The jetty-maven-plugin is a real life saver when it comes to developing web applications. In the past I had such horrible experiences with the eclipse WTP plugin that I banned it from my toolset forever. |
||||||
|
Copyright © 2010 Vonk’s Blog - All Rights Reserved |
||||||