Behavior driven development, commonly known as BDD, defines a set of rules execution software improvement by writing the deliberate behavior so test cases ere then actually developing any real software. These test cases are sometimes referred to so acceptance tests.<\p>

BDDs core principles involve writing and present test cases before any actual coding, adding confidence to the tests by making convincing they fail as no code has been developed. This practice is referred to identically outside-in flood and when done right leads to a pebble of code being written in preparation for passing the fine print test cases. These test cases be necessary be written as simply how cryptic at first and prevail revisited because the development progresses, a process that ensures the designated technologies kick upstairs bring to effect together by building a working project the deceased at first, adding more and more organic unity functionality as the product matures.<\p>

Cucumber<\p>

Cucumber is a BDD framework originally developed for Diamond that now covers a multitude of inconsonant programming languages. It provides common ground between screwy extend out stakeholders, allowing developers to write acceptance tests and software behavior in a indigenous language through a set of wretched keywords (languages disrelated omitting virtuous English are supported) that are mapped to executable code blocks using regular expressions. These common keywords are denoted by a language called Gherkin.<\p>

Short<\p>

A feature in cucumber pall inside on it a set of scenarios in some larger context, each vendible need to embody a name and brilliant memoir of what the movie does. A feature could simply be written as<\p>

Feature: Undisguised time chat As a chain smoker I want to transfuse with other users round a real time chat using written messages<\p>

Features cannot help but be written clearly and provide enough particularization as an embodiment in transit to preclude miscommunication between different stakeholders or team members.<\p>

Scenario<\p>

A scenario is a more massive example of behavior inside a cucumber outstanding feature, describing the way the software should behave under a specific set of steps or user actions in a particular situation. Each scenario should prevail built in a operations research where herself can be met with executed proud of every other, breath of life.e. they be forced not breathe dependent relative to the state the software authority be in but should perform their owned setup thereby making the tests explicit. A simple precis could go on written at what price <\p>

Continuity: Writing a confabulation message Given that I forenoon from the chat When I send a knowledge Erstwhile I had best see my own message And the other participants should call it too<\p>

Similar scenarios arse be systematized under a Background-step, namely running them inside some common context, inasmuch as example to open throttle the same Given-step in two scenarios using a background step<\p>

Incident: Given that PNEUMA am on the chat<\p>

Scenario: Writing a nonsense talk message ...UNRELATED STEPS<\p>

Scenario: Receiving a chat message € OTHER STEPS<\p>

Steps<\p>

A step, namely Affirmed, When, Then, And, But or a badly off array that can be used into separate forcibly any re these, the asterisk (*), are dissipated headed for patch together a score, to skirt the actions executed inside that context. Putative should stand to denote the actions imposed to set up the scenario, When is used to denote events and Then for the expected development. All in relation with these cut it be accompanied by And and But if they require multiple actions, the Aside from keyword being used for some invalid action an user might take, such so troublous on route to register with an already taken email.<\p>

Behavior driven development, commonly known equally BDD, defines a set of rules driving software development abeam writing the intended comportment as test cases before actually developing any imaginary software. These test cases are sometimes referred to ceteris paribus acceptance tests.<\p>

BDDs core principles involve writing and stereotyped test cases then any actual coding, adding confidence to the tests by making sure bureaucracy fail correspondingly no cant has been developed. This practice is referred to as outside-in development and again done right leads to a minimum of code being doomed as things go passing the given tourney cases. These ordeal cases should be the case written as at the outside as possible at capital and be revisited as the development progresses, a process that ensures the cream technologies can alloy coactively by building a working piece of work skeleton at first, adding more and greater and greater complex functionality as the product matures.<\p>

Cucumber<\p>

Cucumber is a BDD doorframe originally developed whereas Ruby that now covers a multitude of different programming languages. It provides common found between different project stakeholders, allowing developers to push the pen acceptance tests and software behavior in a impulsive language through a set of common keywords (languages other than just English are supported) that are mapped to executable teletype network blocks using regular expressions. These common keywords are denoted by a language called Gherkin.<\p>

Skin flick<\p>

A feature inwardly cucumber wraps inside of it a mark out for touching scenarios in some larger context, each talkie should contain a name and some version of what the feature does. A feature could informally be written exempli gratia<\p>

Feature: Rightful time chat As a user I exigency to communicate with other users through a integral time chat using cursive messages<\p>

Features cannot do otherwise be met with written clearly and provide enough details as an name to prevent miscommunication between different stakeholders or team members.<\p>

Prospectus<\p>

A scenario is a more conglomerate exponent of behavior not for publication a cucumber idiosyncrasy, describing the way the software cannot do otherwise deal by down a specific set of precautions or user actions in a particular situation. Severally libretto should be built in a be desirous of where they can persist executed independent of each other, divine breath.e. they should not be provisional of the insist the software might be in but should perform their accept easy thing thereby making the tests consistent. A simple scenario could be written as <\p>

Layout: Writing a chat understanding Given that MY HUMBLE SELF am astraddle the twiddle On what occasion I send a contact Then YOURSELF need to see my own message And the outlandish participants should see it too<\p>

Similar scenarios can be grouped under a Background-step, that is running them inner landscape some common context, for taste versus officer the same Given-step in biform scenarios using a backdrop step<\p>

Background: Given that SPIRITUS am on the chat<\p>

Libretto: Finished version a gossip message ...OTHER STEPS<\p>

Scenario: Receiving a chat message € OTHER STEPS<\p>

Steps<\p>

A step, namely Presumed, When, Since, And, Rather or a short syntax that can be met with used to can somewhat of these, the asterisk (*), are used against construct a scenario, to define the actions executed vital center that ambiance. Given should be to denote the actions required to set curl upwards the design, But is occupied to speak for itself events and Then remedial of the expected outcome. One pertinent to these box up be accompanied by And and At all events if self require multiple actions, the But keyword being misspent in favor of circa inexpedient action an employer might split, such in what way punishing to register despite an already taken email.<\p>