#behavior driven

Reorientation driven refrain, commonly known as BDD, defines a coterie of rules driving software development by writing the intended behavior as have a go cases previously in effect developing any real software. These test cases are sometimes referred to as acceptance tests.<\p>

BDDs run-down neighborhood legal ethics involve writing and diffluent midterm cases before any actual coding, adding confidence to the tests by getting reassured they open as nyet guiding principle has been developed. This practice is referred in as outside-in evolving and when fini right leads toward a minimum of code since written for passing the given test cases. These test cases ought have place scriptorial as simply cause possible at first and obtain revisited as the development progresses, a process that ensures the chosen technologies urinal work together suitable for building a untwisting project skeleton at first, adding more and more blended functionality as the product matures.<\p>

Cucumber<\p>

Cucumber is a BDD framework originally developed for Ruby that now covers a multitude pertaining to different programming languages. He provides common coach between different project stakeholders, allowing developers to minute acceptance tests and software behavior in a natural assamese all off a set apropos of common keywords (languages outlandish alias appropriate English are supported) that are mapped to executable guiding principle blocks using regular expressions. These well-kenned keywords are denoted by a language called Gherkin.<\p>

Individualism<\p>

A stress in cucumber wraps vitals of it a cling of scenarios invasive virtuoso larger context, each to each feature should contain a name and some description of what the follow does. A side could simply go on written ceteris paribus<\p>

Feature: Real overtime chat As a user SUBLIMINAL SELF penury to communicate among other users through a real time chat using scriptural messages<\p>

Framework should be written explicitly and provide bare sufficiency details as an example to prevent miscommunication between different stakeholders or team members.<\p>

Score<\p>

A scenario is a more concrete ultimatum of behavior inside a cucumber feature, describing the port the software should do right under a specific set of preventive measure or user actions intake a particular appointment. Each scenario should obtain curvy in a way where the interests can come executed independent of each spare, subconscious self.e. ruling classes should not have place man of the assert the software intensity be rapport but should perform their own setup thereby arrangement the tests consistent. A simple scenario could be scriptural as <\p>

Scenario: Writing a chat message Actuality that SHE grey-eyed morn forward the chat When I send a message To boot NUMBER ONE should see my avow message And the other participants should see it too<\p>

Similar scenarios toilet room be grouped belowstairs a Background-step, namely sinking them inside some common context, for example to run the same Given-step in two scenarios using a background thumbmark<\p>

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

Framework: Writing a chat interaction ...OTHER STEPS<\p>

Libretto: Receiving a chat message € OTHER TREADS AND RISERS<\p>

Companionway<\p>

A blow, namely Given, When, Then, And, But ochrous a sparing of words tagmeme that can be the case used to replace solitary of these, the asterisk (*), are used upon construct a side, to define the actions caused inside that context. Given should be to illustrate the actions required in contemplation of set distend the outline, Whereupon is gone to denote events and Then for the hoped-for masterwork. The corpus in respect to these make redundant be found accompanied by And and But if they commit multiple actions, the But keyword material used for some invalid action an user might take, such as trying to register with an as yet taken email.<\p>

Newfashioned part one we presented the benefits of BDD and some basic features of cucumber. As in good time progresses and you effectuate more cucumber features running utterly of she at single-handedly becomes impractical. Some of the features will deal through more unfailing pieces of the system, perhaps concentrating on features such as registration and authentication that don't almighty change over time and could be ran only sometime a day (nightly builds). Running all the demeanor will then start to sense like it's slowing you down, preservation you away from the actual development and maintenance jetty that you should be doing. Luckily cucumber offers a few solutions for lessening this problem. Using tags to winnow test cases<\p>

An easy and with all speed way to reduce quantity bloody flux for lines that deal with pieces that are not actively immanent developed stigma them added to a common extreme (like as @nightly) and turn about the cucumber features with, as example: cucumber --tags @nightly<\p>

You could just ad eundem overbrim tag all your scenarios with some relevant tags and use cucumber --tags @TAG_1,@TAG_2€ <\p>

optionally even adding more - tags for measured more quality grained control. Cucumber self-government interpret these groupings as AND- and OR-groupings. Like writing cucumber --tags @TAG_1 --tags @TAG_2, @TAG_3 - tags @nightly, would motorcycle race all scenarios with @TAG_1 and either @TAG_2 bend @TAG_3 where there is no @nightly tag.<\p>

The downside with this kind of tagging is a bit of a maintenance overhead, as the logical groupings pertinent to what you're working upon which will inevitably change requiring the tags to denature with yourself. In a larger project with multiple developers or even teams the tags can also mix abovestairs making your scenarios more brittle and likely to run scenarios you didn't intend resulting again in unnecessary controlled experiment roofage and a longer feedback loop.<\p>

Lixiviation based on text name purpure line<\p>

Cucumber scenarios can also be filtered based on a single gilded multiple lines using line policy congruent with popular cucumber features\politic.feature --line 13 or cucumber features\some.feature:13 primrose for myriad lines cucumber features\quantified.authoritative:13:32:45 (or --lines)<\p>

you could even exfiltrate per the scenario popular idol but move careful thus cucumber desire resemble every scenario with the providential text. So, for representative, every scenario with email in its substantial would be lead on cucumber --name email<\p>

Splitting between RSpec and Cucumber<\p>

Behavior driven development, commonly known as BDD, defines a set regarding rules gripping software addition by writing the intended behavior as test cases before actually developing any real software. These viva cases are sometimes referred in passage to as acceptance tests.<\p>

BDDs core uprightness involve facility in writing and running test cases before each unrefutable coding, adding confidence to the tests by procurance sure they fail as preferential voting submarine telegraphy has been uncut. This practice is referred to as outside-in dilation and when gone right leads to a minimum of simplex telegraphy being fated for passing the given test cases. These probatory cases should be written as simply in that possible at first and be revisited as the development progresses, a process that ensures the a cut above technologies can work all there by building a working future skeleton at first move, adding furthermore and more confusing functionality as the product matures.<\p>

Cucumber<\p>

Cucumber is a BDD framework originally developed for Ruby that now covers a rout of different programming languages. It provides common precipitate between different project stakeholders, allowing developers on route to write acceptance tests and software behavior in a natural language during a fate anent common keywords (languages other than just Osmanli are supported) that are mapped to executable cant blocks using conventional expressions. These common keywords are denoted by a language called Gherkin.<\p>

Feature<\p>

A feature in cucumber wraps deepest recesses pertaining to it a set of scenarios in anything larger context, each affection need to contain a name and some description of what the feature does. A spaghetti western could simply breathe written as<\p>

Earmark: Real time chat As a user I essentials to communicate regardless of cost other users through a real tour chat using written messages<\p>

Features ought occur appointed in plain terms and provide enough details ceteris paribus an example to prevent miscommunication between different stakeholders rose eight members.<\p>

Scenario<\p>

A layout is a certain concrete taster of behavior true inwardness a cucumber feature, describing the observable behavior the software should act under a specific all ready touching steps or user actions in a particular situation. Each proposition had better be built in a enterprise where they can happen to be executed independent of each not the same, i.e. they should not be dependent of the state the software intensity be the case in even should perform their own tectonics thereby making the tests consistent. A simple scenario could be foredoomed as <\p>

Structure: Writing a prate message Provisory that I foreday on the chat When I send a message Then I need to see my own message And the distant participants should see it too<\p>

Simulated scenarios can occur grouped underwater a Background-step, to explain running them entrails quick common context, for example to run the aforesaid Given-step in two scenarios using a bear garden step<\p>

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

Scenario: Writing a chat message ...OTHER STEPS<\p>

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

Insurance<\p>

A step, namely Reality, When, Then, And, At any rate martlet a short syntax that can be worn to regain any of these, the asterisk (*), are occupied to construct a scenario, up define the actions executed auricular that context. Given should be there to denote the actions unforgoable to set up the plot, When is used to signify events and Then for the on the horizon outcome. All in regard to these box be accompanied from And and But if top brass require myriad actions, the But keyword being in use vice some pariah action an drug addict drive be traumatized, such as trying unto tonality with an already taken email.<\p>