SpecBind is an extension to SpecFlow that uses common language steps to allow a user to define interaction with an application. Unlike conventional SpecFlow where the user needs to define how each step definition interacts with the host system, SpecBind uses conventions and a thin page model to minimize coding efforts and maximize flexibility when defining the link between specifications and working sites.
Getting SpecBind installed is a simple process:
-
Go to http://www.specflow.org and follow the instructions for installing the Visual Studio Extension
-
Choose the driver type you want to use to interact with the host system:
- Coded UI
- Selenium
-
Create a new test project in Visual Studio, Make it a Coded UI project if you are using that.
-
Install the NuGet package for SpecBind
And you're done!
One of the key features of SpecBind is it features a common set of steps that can be used to describe actions you take in validating a web application. These steps are outlined by their functionality in the Getting Started guide or in the Step Reference section. One thing to note is how they work with the Gherkin language. For any Given steps the step is in the past tense. This is because it assumes the action is a prerequisite and has already occurred. The When and Then steps are in the present tense since they are what the test indicates should occur. In this guide, both commands will be outlined so that the syntax is know, but only the present tense will be used for examples.
Build Status:
Follow the Getting Started section to begin creating tests, or Documentation for in detailed information on SpecBind.