In this section we will concentrate on more details on BDD Framework. In traditional waterfall model, client will give a BRD document. From BRD document, developer have own perception and develop based on his perception. Same way Tester will have their own perception and test the application based on his understanding. There might be the mismatch between their different perception. But in BDD Test cases is defined in a Business level by following ubiquitous language. Ubiquitous is a semi-formal language that shared by all team member of the project both developer and tester
In the BDD Framework, we don’t write Test case directly though we have test Scenario. Here you don’t have any Business requirement to start a development or testing of the application. The Business requirement will be the form of Test case. You don’t have any document for the requirement in BDD. Developer will take this Test case as reference to develop his component and QA will again take the same test case to test that component.
Here there is a concept we will discuss now is Feature file. Feature files contain the Test scenarios not Test cases. Test scenarios are written by QA Team or Test Manager but this is understandable by the Non-Technical people.IN feature file each feature contains the Steps. Once you create the feature, Step Definition File define the steps in Feature file.This use the java with Selenium to implement the Test Step. In the Next Stage we can execute the step definition by using Test Runner class.
Now we are clear about how to write the BDD test case in feature file and step definition file. In next section we will understand more about BDD with practical example and will check the advantage and disadvantage of the BDD. Addition to this we will discuss some bit of Regx.