
We will discuss about Gherkin syntax in detail in this video
In this video, we will introduce Specflow
In this video we will understand how features files and step definitions are working closely together to get the job done.
We will talk about Specflow Scenarios and how to work with scenarios in feature file.
In this video we will talk about Tables in Specflow and how to work with multiple data using Table Class of Specflow from feature file through step definitions.
Working with dynamic tables using Specflow.Assist.Dynamics
In this video we will talk about Specflow bindings and advanced binding types
In this video we will talk about Specflow+Excel plugin which is not FREE plugin though, but still helpful to understand what feature it has got. We will discuss about Specflow+Excel plugin in conjunction with Examples of Scenario outline.
This video address one of the issue happens due to Specflow+Excel plugin with Visual studio 2015, this issue may go soon in next update, but till then, this video is helpful !!!!
Sometimes, we may face no test in Test Explorer issue, this issue will be fixed in this video !!!
In this lecture we will discuss how to work with FindInSet to verify Collection of data and Specflow Table.
This course will enable one to understand the complete End-to-End code development using Specflow and integrating Selenium with Specflow feature files and scenarios by leveraging the power of Behavioral driven development.
The aim of this course is to give all the information you need to understand the basics of Gherkin language specification, Behavioral Driven development (BDD) and how to write scenarios to run Selenium test in much easier way with Specflow.
Again, this course, will not cover any basics of C# programming languages or Selenium automation testing, rather, we will directly discuss about the nitty-gritty details on Specflow and its great features to create much robust features and step definitions.
We will also see the power of Visual studio IDE intelli-sense working seamlessly with Specflow while writing feature files and mapping step definitions with various different classes (which is highly nagging while working with cucumber in ruby language)