After making the graph and tests tester executable, we now focus externally and ensure there is readability from a business perspective. The next principle is “Make it Business Readable.” As you know, Behavior Based Testing has its roots in Behavior Driven Development (BDD). One of the drawbacks of BDD is the text based nature of the feature files. Getting the business to verify these is a challenge. BBT uses the cause and effect graphing to give a visual representation of the outcomes and the requirements needed to achieve them. This is awesome; because once you have graphically mapped the business’ requirements to the expected results AND done this in a consumable way, then your BBT graph can be used for sign-off.
This principle allows you to take your graph to the business and go straight from sign-off to generation of your test cases; but this is all for naught if the business is unable comprehend it. In the previous principle, you put yourself in another tester’s shoes. Here, you are putting yourself in the place of the business and looking at the graph from their perspective; making sure the graph is easily understood and able to be verified. Remember, you are the expert on your business partner. How are they going to be able to consume it best without violating the other principles? That’s the essence of this principle.