Specflow BDD: C# Testing Mastery

Today we will discuss the following:

• What our project that we will work is.

• How we manage to work at it.

• What do we want to do with it.

• How it is related to real-life projects you will work at.

Today we are going to discuss what the project that we will have at the end of our tutorial is and how it is related to real-world projects.

Today we will learn:

• Brief BDD introduction

• The basics of BDD

• The BDD process

• The BDD benefits

• Why BDD is needed

Today we will learn:

• Brief description of a real-life sample of BDD

• Main Principles of pure BDD

• Key components of BDD at a project

• Real-life application

• BDD benefits in the example.

• Why it is nice to apply BDD to a project.

Today we will discuss the resolution of the following home task:

• Create a BDD scenario for an e-commerce website.

• Select an area of your interest (any flow at an e-commerce website).

• For an explanation of the home task, order placement in a shop card scenario will be used.

• User Given-When-Then format

• Try to use only one When step

• Use commonly understandable language for it.

Today we will learn:

• Brief history of SpecFlow BDD in C#

• The main features of SpecFlow C#

• Advantages and disadvantages of the tool

• The similarities with other C# BDD libraries.

Today we will learn:

• What is IDE?

• What are the most popular IDEs for C# development?

• Why Visual Studio?

• How to install Visual Studio to your machine?

• How to perform the basic configuration of Visual Studio?

Today we will learn:

• .NET Versions – which one to use?

• How to check the current .NET version.

• How to download .NET installer.

• How to install .NET via installer.

Today we will do the following:

1. Add SpecFlow NuGet package.

2. Add SpecFlow.Tools.MsBuild.Generation NuGet package.

3. Add SpecFlow.NUnit NuGet package.

4. Add features and steps folders.

5. Make sure all the packages are loaded.

6. Install SpecFlow extension for Visual Studio.

Today we will do the following:

1. Create TwoNumbersAdditionSteps class in steps folder

2. Create twoNumbersAddition.feature in features folder

3. Create a scenario with two Given, one When, and one Then steps

4. Create step mappings in TwoNumbersAdditionSteps class.

5. Store NumberOne, NumberTwo, and result in separate fields of the class.

6. Assert two numbers sum with NUnit assertion.

Today we will do the following:

1. Add getBoards.feature to features folder

2. Add GetBoardsSteps in steps folder

3. Copy-paste RequestWithoutAuth() and RequestWithAuth() methods from BaseTest class.

4. Set RestSharp base URL in requestWithoutAuth() method

5. Convert each line of CheckGetBoardTest into BDD step def.

6. Create request and Response private fields in GetBoardsSteps class.

7. Make all assertions via NUnit.

Today, we will discuss the following:

• Migration of NUnit 3 test to SpecFlow BDD Scenario.

• Scenario steps definition in feature file.

• Scenario steps mapping in Steps class.

• Merge of similar steps into single.

Today we will:

• Discuss SpecFlow step parameters.

• Install Cucumber Expressions Specflow 3-9 package.

• Inject dynamic query params for REST Request.

• Merge path params setup steps into a single step.

• Use a single step for checking any status code.

• Verify response against any JSON Schema.

• Verify any body param for any expected value

The home task for today's lesson is:

• Transform UpdateBoardTest class into feature file.

• Parameterize the request is sent to endpoint step.

• Add step that passes body params to REST request.

• Use hard-coded value for updated board name temporarily.

Today we will do the following:

• Discuss what Data Table in SpecFlow is.

• See where Data Table is used.

• Add data table for query and path params injection.

• Use data table with headers.

The home task for today is:

• Transform as many parameters as we can to data tables.

• Use data table for response body validation.

• Initialize request body as data table dictionary.

Today we will do the following:

• Migrate board validation tests to Outlines

• Split feature files by packages.

• Remove already migrated NUnit test classes.

• Add 'request without auth' Given step.

• Add step to check response body as string.

The hometask for today's lesson is massive:

• Migrate update, create and delete board scenarios to outlines.

• Delete migrated Test classes.

• Delete unused validation arguments holders and providers.

• Delete unused Boards Endpoints URLs.

Today we will discuss the following:

• What are Backgrounds.

• How are the Backgrounds used.

• Apply Background for Get Boards feature.

• Why no hometask is needed today :)

Today we will:

• Create TestContext class.

• Put all data to share to TestContext.

• Learn what ThreadLocal is.

• Wrap all data to share with ThreadLocal.

• Split your steps into action and assertion.

The hometask for today's lesson is:

• Use more elegant way to share test data.

• Get rid of static keywords in your test context.

• Inject TestContext as your step classes' fields.

• Run all the tests to check your updates.

Today we will:

• Learn what Step Arguments Transformers are.

• Merge two steps to create request.

• Create an enum to store endpoints.

• Use arguments transformer to work with the enum

The hometask for today's lesson:

• Remove key and token from scenario.

• Create a IDictionary Transformer class.

• Use [StepArgumentTransformer] attribtue.

• Store key and token values in Constants class.

Today we will learn:

• What are hooks and tags in SpecFlow.

• Add Delete Board feature.

• Add a step to assert board absence.

• Add a hook to create board before scenario.

• Add Request Auth provider class.

The hometask for today's lesson is:

• Add Create Board feature.

• Run a deleteBoard hook after scenario.

• Add a step to assert board presence.

• Remove migrated tests.

• Remove not needed contants.

Here is our agenda for today. We will learn:

• Why do we need to run tests via CMD?

• Which dotnet tasks can be used to do so?

• How to run our tests via CMD?

• Where test results report is stored?

Today we will do the following:

• Attach Extent Report to our project

• Configure report in Hooks.

• Add hook to print response to report.

• Investigate how generated report looks like.