SpecFlow is an open-source project used by SpecFlow to save an acceptance criterion for various features (use cases, user stories) in the application as prescribed by the Gherkin syntax. . Usually the source code is hosted on GitHub.
The Gherkin format was invented by Cucumber and used by other BDD tools also. The Gherkin language is considered as a project on GitHub − https://github.com/cucumber/gherkin
The main features of Feature elements are −
If the scenario includes more than two steps then it is called as multiple scenario steps. Then three types of steps that describes the preconditions, actions or verification steps, which make up the acceptance test.
Tags are called as markers which can be allocated to features and scenarios. Assigning a tag to a single feature is equivalent to assigning the tag to all scenarios included in the feature file. A Tag Name with a leading @ denotes tag.
The background language element is used to mention the common precondition for all scenarios included in a feature file
Scenario outlines are designed to explain about data-driven acceptance tests. The scenario outline includes various scenarios of a scenario template specification (a scenario with data placeholders using the <placeholder> syntax) along with a set of examples which provides values for the placeholders
To add comments to the feature files at any place start with #. Make sure that the comments in your specification will be a sign that acceptance criteria have been mentioned wrongly. SpecFlow ignores comment lines.
Behavior Driven Development Related Interview Questions
|Software Development Lifecycle (SDLC) Interview Questions||QUnit Testing Interview Questions|
Behavior Driven Development Tutorial
Behavior Driven Development
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.