Working Software vs. Comprehensive Documentation — BDD Makes the Save

  • a client and a team to get on the same page about the requirements and functionality of a project;
  • a team to better understand the project and give accurate estimate of implementation;
  • a team not to lose a tiny detail, which is important for a client or a project;
  • a QA team with manual functional and regression testing;
  • everyone, when scenarios are automated, because it saves a lot of time and money and gives a certainty in quality of the result;
  • a client, who gets not only the source code, but a source code with live documentation.
  1. It all starts with the understanding of TDD philosophy: in order to make something right, you shouldn’t start making it ASAP, but think of how you will make sure you did right things.
  2. It carries on with the understanding of value and importance of BDD as a process of communication of the entire team. Without specification by example, everyone in the team can get the requirement in their own way.
  3. And finally, it ends with understanding that without written acceptance criteria by ATDD it’s not possible to get the result accepted and make sure it is a quality one.
  • making a glossary for scenarios;
  • making template scenarios, widely spread among various projects;
  • cross-platform tools for automation;
  • education sessions for those teammates, who have never created scenarios before.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Rosberry

Rosberry

Rosberry is a mobile app design and development company based out of Thailand. We design, build, test, deploy and support apps at scale.