Abstract: Do you remember your childhood when your mom or an older story teller pronounced the most interesting words in the world? “Once upon a time…” Let me be now your story teller, listen to my story about a legacy app, a painful problem, the search for the solution and the lucky outcome.
No, no, this is not the story about a new green field project where everything is so clear. However, even in this story there is a master builder, who shows the developers how to scaffold the legacy app with BDD scenarios using SpecFlow or Cucumber and everything will be all right in the end. Let me tell you about different strategies, collaboration and testing patterns that can be followed in such a renovation-like situation.
So, are you ready...? “Once upon a time there was a company where…” To be continued at my session...
Learning Outcomes: - Is it possible to introduce BDD for legacy projects?
- What are the different strategies, collaboration and testing patterns that can be followed?
- How can we address complex test automation problems by making small steps and using temporary infrastructures?
- How to address change requests and bugs? What are the differences?
- How to balance the different kinds of tests to get to the "testing pyramid" model?
Attachments:
