The Robot Framework is a very versatile tool and never confronted us with unsolvable problems so far. In some regards it still feels a little rough and needs some polishing, to make development and maintenance of automated tests more efficient. One of those areas is the integration into the well known development environment. There is the Robot IDE, but this only covers a fraction of my requirements. The following will show, how easily the Robot Framework and your own Java Keywords can be integrated in Maven and Eclipse.
read more…

Screenshot are incredibely helpful when doing user interface tests, to get fast feedback why a test has failed. Selenium provides several great opportunities to do exactly that. But, there are many problems related to that at the moment, from which some will discussed, even solved in the following post. read more…

When doing ATDD (Acceptance Test Driven Development) or BDD (Behaviour Driven Development), the following grammar is widely spread to formulate pre- and postconditions of a test:

1. Given: The static preconditions
2. When: The behaviour under test (or that, which should be specified)
3. Then: The expected results of the behaviour under the given preconditions

In this context executable specifications are a hot topic, but it is still a long way to go, isn’t it? read more…

… by Slobodanka Sersik and Dr. Gerald Schröder

The context of this session is a container management system, which is rather big, speaking about 200 person years effort. The model that was used in order to create the test cases included scenarios, steps, adapters, components, and simulators. read more…

The keynote starts with our dear agile chicken & pigs story. Pigs are the ones who are fully commited to the projects, all other stakeholders are chickens. Judged from the agenda, this session will be much about required skills and motivation. That sounds promising

What’s special about agile teams? read more…

Are you now or have ever been … on a team that was pressed or overruled into releaseing flawed or unfinished work? I guess everybody has. After in introduction to Scrum he comes to the value of the “Definition of Done”. How it helps to have consensus and common understanding, manages expectations so that a release does not surprise the customer and have repeatable quality.

You should have a Definition of Done on different levels, for Tasks, Stories, Sprints and Releases. For example:

read more…