The FinalBuilder guys recently released FinalBuilder and FinalBuilder Version 6. Hadi already blogged about that and that IntraWeb is going to be built continuously.

We will not just have continuous builds, but we will also run DUnit tests continuously. We don’t have too many test cases right now, but the number is increasing and we will instantly be notified once somebody checks something which makes any of our test cases fail.

The cool thing is, that you can use DUnit even for Memory Leak detection. We didn’t have many mem leaks in the past, but even if you try to develop carefully, they may happen. With DUnit (in combination with FastMM) we can even for pseudo or session mem leaks. These are leaks where you reserve memory, which will get freed explicitly once the whole application is released, but it should actually be released when you free a form or a session. DUnit creates some sort of Memory state snapshots before and after a test case execution, and then checks if the difference is greater than zero.

Very useful esp. for server-type applications …