Stop the abuse of Given When Then.

Stop the abuse!

Since we read Specification by Example and worked on the (old) Living Documentation competence center, we teach all proxies about using Given When Then to express business rules tests BDD style. But this mantra has become the standard for expressing all kinds of tests, often introducing scripted testing, mixing the UI with business rules and back-end, making the automation almost impossible. Also I see lots of mixing the given (starting point) with when (action) ...

Let's come together with examples of our respective projects and find out how we can reverse this situation and give the Given When Then mantra the use is was invented for, so that automation becomes much more feasable. Also let's discuss what is the best way to express UI tests, end-to-end tests, ...

Goal of the exploration days is to have a document with tips and tricks for agile teams on how to describe the tests in the different layers.

And NO this is not a session for proxies only. I hope you developers want to help us with your view on the subject so that the end product is one for the team!