BDD living documentation for Product Owners



  • We have been using bdd in our team for over a year now. The jobs that run our tests generate a published report in business language that anyone is available to read.

    We find these very useful inside our team for when tests fail etc. but our business do not seem to find this documentation useful as a communication tool. I'm not sure if it is the GWT language or the format of our report or just a general lack of interest.

    If anyone is using the same approach have you found that the business find this living documentation useful?

    If so how have you made this possible? Any experience shared would be great thank you.



  • To be honest this sounds like the very issue that seems to have split the BDD tools. You either have tools that produce specifications during the test runs, ao that you know exactly what your system is capable of doing. Or you have tools that consume specifications so that you know how compliant your application is with the specifications.

    In the first case this means that tooling like mspec is used to translate code into a readable specification which can be presented back to the business so they can verify it. My experience is very much like yours, they aren't interested. It simply is an overhead in the process they can do without.

    In the second case however we catch them at a point where they are much more engaged. They want development to occur so they get a positive benefit, and they are very happy to tell us how they want it. I have found this is the time to use BDD specifications. In fact it has several advantages done this way round.

    The specification only has to be reviewed once by the business. If they are involved in making the change to the specification then it can be treated as a formal criteria during every testing cycle, if we meet it, we are done, no need to get them to review it.



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2