Agile Testing: Getting things Done!

Posted by Cirilo Wortel in the early morning: May 13, 2008

For some years now I have been working as a tester in agile projects. In our projects we are trying out new ways to integrate testing into the development cycle and ideally to offer a complete project solution to our customers. In my vision the perfect offering would be to create working software with each development cycle, which has the actual ‘Done’ status. Not only ‘Done’ from a development point of view, but actually ‘Done’ from the customer perspective as well.
(more...)

JavaOne 2008 Day Two

Posted by Jeroen van Erp mid-morning: May 8, 2008

Today was the second day of the JavaOne 2008. Besides doing a lot of chatting in the JavaOne pavillion, and visiting all the cool parties this night, we also went to a number of sessions. Also today the NLJug had the James Gosling meeting we won for being the biggest JUG out here. After a long day of work, we finally had time to relax at the Adobe party and at the SDN party.

Todays topics included:

  • Closures
  • JavaFx, Groovy and Google Android
  • Swing GUI testing
  • Scripting

(more...)

Helpful error messages in Grails

Posted by Erik Pragt around lunchtime: May 4, 2008

Currenttly, I'm in the process of building a Grails application. While I've built several prototypes/quick hacks, this is actually the first 'real' application I'm building. "So", I thought, "if this is a real application, I'm in need of some real tests!". When you're in the normal flow of developing a Grails application, everything goes so fast, you almost forget about writing the tests. So I decided to do it a bit differently, and do it just like in Java: do it TDD!
(more...)

Automatic test data generation

Posted by Erik Jan de Wit in the late afternoon: February 28, 2008

We’ve all being there, we’ve all had this on a project once or maybe even more times. The assignment is to build an application but there is no data for you to work with. There could be any number of reasons this could be the case - to name a few, the web-service that should be connected is not done in time, the database migration is postponed. Then someone has to create database scripts with test data, or implement a test web-services. This is all a waste of time.

But lucky for you now there is a solution.
(more...)

Unit Tests As Throw Away Design

Posted by Jan Vermeir in the late evening: January 15, 2008

Unit tests are brittle: if you change the class under test there’s a more than average chance that you will have to change a load of unit test as well. On the other hand unit tests help you think about design on a micro level. The test shows what a method is supposed to do, without room for the interpretation errors you get when using abstractions as design.

So, should we use unit tests or not?
(more...)

Testing with(out) aspects

Posted by Jeroen van Erp in the late evening: September 26, 2007

Recently I wanted to add an aspect to some domain object, so that it was saved, the moment it changed state. However, after adding this aspect, the whole build of course failed, because a lot of the unit tests weren't expecting the calls which were now woven into the domain object.
(more...)

Files in a distributed transaction

Posted by Meindert Deen around lunchtime: September 25, 2007

At a client we are now using files and datasources together. We want the write actions to the database and the files to be in one transaction. We want this because the files represent the database data for legacy applications. As there is no distributed transaction API for files which is JTA (Java Transaction API) compatible we had to find a solution to implement this. This post describes the (big) steps we did and the solution we found. Of course, you can skip the steps and go straight to the solution. ;-)
(more...)

FitNesse Refactorings

Posted by Lars Vonk mid-afternoon: August 25, 2007

I like to share some FitNesse refactorings which I think are quite useful. These refactorings will help you prepare your tests for those eternally changing requirements. This is the scenario:

(more...)

Transactional unit test over multiple datasources

Posted by Lars Vonk in the late evening: July 31, 2007

Recently I needed to write an integration test that covered a transaction over multiple SessionFactories and different datasources. I wanted it to be an outside-the-container-test and therefor I needed some ability to do transactions over multiple datasources without all the stuff a J2EE container would provide.
A good start for writing transactional tests can be found, as usual, in Spring. All you need to do is to extend the AbstractTransactionSpringContextTests class and the rest is a piece of cake. Now the question is how to wire this up for multiple datasources?

(more...)

Mocking Super Calls

Posted by Jeroen van Erp at around evening time: June 25, 2007

Another installment in our mocking adventures. After I presented you last week with some possible solutions when you're mocking static method calls. Today I am facing a different problem.
(more...)

Next Page »