In this process, there are three main people involved. One, who manages the prerequisites like a Business Analyst or a Product Owner. Second, an individual who designs executes and creates it like a developer. The third primary person is the one who is going to test and guarantee it.<\/p>\n
These key people examine the feature which has to be implemented and discuss various use cases and how the system needs to carry on at different point of time in different situations. Further, these practices are noted down as scenarios which become the written document of how the system has to behave in various cases.<\/p>\n
Language And Platform Compatibility<\/h2>\n
Cucumber Implementation<\/strong> is available in open source languages like Python, PHP, Java, Ruby, etc.<\/p>\n Framework Integration:<\/b> Cucumber is integrated and supported by frameworks like Waitr, Capybara, Ruby on Rails, Selenium, etc.<\/p>\n To understand Cucumber, we have to know each of its features and usages. These are described below.<\/p>\n 1. Feature Files:<\/b> The syntax\/format in which these feature files are written is called Gherkin; this provides with an arrangement of guidelines which should be taken after composing your feature file. These files should have an extension \u2018.feature.\u2019<\/p>\n Scenario:<\/b> The description following this keyword gives the expectation of this test case or scenario, as to what is being checked and in what conditions. To make a scenario more readable, Gherkin offers a few keywords which you can likewise call as clauses.<\/p>\n Given:<\/b> Given condition speaks to the pre-conditions required for the specific situation and if your situation requires more than one pre-condition, “AND” clause can be used immediately after\u00a0the ‘Given’ condition.<\/p>\n When:<\/b>\u00a0Any statement that begins with ‘when’ clause represents the steps-to-execute part of the test case document. It contains the executions steps that are specific to this scenario. In the majority of such\u00a0circumstances, this section contains more than one step and hence along with this clause we also use the AND clause as well.<\/p>\n Then:<\/b>\u00a0Any statement that starts with this clause represents the verification steps and the expected result of the scenario. On the off chance that this part likewise contains multiple steps, then AND clause is used alongside.<\/p>\n a) IDE that we will use to write our feature files and all the code behind. a) cucumber-coreCucumber Basics<\/h2>\n
\nThese are the\u00a0typical test case files in a BDD process and furthermore, go about as living document to the business necessity and a bridge between the requirement documentation and implementation part of it.<\/p>\nConfigure Java Environment for Cucumber Execution:<\/h2>\n
\n
\n
\nb) When it starts up, choose a workspace.
\nc) Click on Help\u2013Install New Software, Add plug-in from http:\/\/cucumber.github.com\/cucumber-eclipse\/update-site<\/p>\n\n
\n
\nb) cucumber-java
\nc) cucumber-junit
\nd) cucumber-jvm-deps
\ne) cucumber-html
\nf) gherkin
\ng) junit<\/p>\n
![\"Untitled\"](\"\/blog\/wp-ttn-blog\/uploads\/2017\/05\/Untitled19.png\")
<\/p>\n![\"Untitled\"](\"\/blog\/wp-ttn-blog\/uploads\/2017\/05\/Untitled8.png\")
<\/p>\n![\"Untitled\"](\"\/blog\/wp-ttn-blog\/uploads\/2017\/05\/Untitled12-e1495106099585.png\")
<\/p>\n![\"Untitled\"](\"\/blog\/wp-ttn-blog\/uploads\/2017\/05\/Untitled13.png\")
<\/p>\n