Transforming the workflow with Behat

One can expect to see references to Behat framework in more technical tracks like DevOps or Coding and development. Test-driven development has become another buzzword, but is it enough for the project success to have someone in the team who knows a little bit of Gherkin?

We argue that the answer is no, and you have to change both project planning and issue flow (whatever project management software you use).

Switching to BDD is so much more than learning Gherkin (or any other language for writing tests). It is a big shift in project planning, writing the code, and then testing it. It is also a shift in the order of statuses every ticket needs to pass before it is marked as done.

We are going to show how this shift was discussed, planned, and implemented in our company - from QA, project manager, and developer perspectives.