Hi guys, today I will post a summary of a meet up that I went about BDD. It was very interesting and more clear than the others texts/posts that I found about.
1 – Communication with all teams (business, developers, tests since beginning) is the key – Everyone should participate.
2 – What is the value of the scenario ?
3 – Could you write in another way/different steps ?
4 – Could you use the same steps ?
5 – Could you join some steps in other scenario to spend less time when you run the feature ?
6 – Your flow is decreasing the possible points of misunderstood gaps ?
7 – Are you doing the scenarios with participation of everyone in the beginning of the project ? When everyone is understanding the same thing and you starts to worry about tests in the beginning of the project, you spend less time/money than write test cases after development. Pay attention in your flow.
8 – Be curious ! Ask !
9 – Everything should be automated ? Remember that the effort spent when you automate something can be less valuable than manual testing.
10 – How many steps are you using in the scenarios, try don’t use more than 4 or 5. Make it simple.
11 – Use page object model – Better structure
12 – Be clear and objective when write the steps
13 – The feature is your documentation for end users, testers, developers. Following one of the Scrum rules, you don’t need more than this in your documentation process. Less time spent, more clear than huge documents (Because it uses examples), keeps the documentation together with the test.
14 – Use 4 layers – Example :
Thanks John F. Smart !
Rafaela Azevedo 