Selenium C# Specflow Learning Path


I always felt there should be a learning path that guides testers through related content to help them to become proficient in Automation.

 I'll attempt to share my learnings and so I have come up with a learning path for automation nerds like me :)

So here are the things we will be talking about 

BDD?

  •  It’s an idea of how software development should be managed by both business interests and technical insights
  • User stories that use the same shared language that your business stakeholders would understand are created
  • The focus is on behaviour
  • All the three amigos i.e. Development team, QA engineers and Product owners should be involved in the scenario identification process, this helps to get a better understanding of business.

WHAT IS SPECFLOW?

  •  Specflow is used to define, manage and execute human-readable acceptance tests in .Net projects
  •   It helps you write specifications using Gherkin syntax.

GHERKIN?

  •  Its business readable, a domain-specific language which can be understood by all
  •   It’s simple
  • We will talk about this in subsequent lectures

AUTOMATION FRAMEWORK

“Automation framework is a program that helps to manage your testing activities “

                                                                                                                      --Amit Tambe
We will talk about framework creation using below technology stack
BDD+ Specflow +C# + MSTest
This was a short introduction, now let’s dive deep into our learning path

LEARNING PATH LECTURES

Part-1: Back to school(Play Group) 👦👧

  1. Object-Oriented Programming Glimpse
  2. C# Basics-Part 1(Class,Objects,Constructors)
  3. C# Basics-Part 2(Namespaces, Properties, Constants, and Read-Only Fields)
  4. C# Basics-Part 3(Method Overloading, Chaining, Overriding)
  5. C# Basics-Part4(Static class and Singleton Design Pattern)
  6. C# Basics-Part 5(Working with strings)

Part-2: Nursery

Part-3: Junior Kindergarten

Part-4: Senior Kindergarten

Part-5: Primary School

Part-6: Secondary School



Please suggest me topics you think should be part of this learning path.
Your views are most welcomed 😎

Comments

Post a Comment

Popular posts from this blog

Specflow -Part3(Working with tables using Specflow.Assist.Dynamic)

In the previous lecture, we learned how can we work with tables to handle test data from the feature file.I will paste the feature and step definitions from earlier lecture and then we will talk about the shortcomings and how Specflow.Assist.Dynamic can help us to overcome them Feature File Feature : SpecFlowFeature2 In order to show specflow capabilities for working on tables We are going to write some scenarios here Scenario : Verify specflow can read data from table and print on console Given  I have dummy student data as below   |  StudentId  |  StudentName  |  Division     |  Age  | |  100        |  James        |  Engineering  |  30   | ...
Read more

Specflow -Part4(Specflow Scenario Outline and Feature Background )

In the previous lecture, we talked about how we can pass multiple data to step using tables, suppose we want to run the same scenario for a different set of data, For example, you want to test the login functionality of an application, where you test login with Administrator, Project Manager, Product Owner etc Here the steps of scenario will remain the same only the login credentials will change according to the user. We can have the same scenario run multiple times for each user you want to test with the help of scenario outline, check below Feature file Feature : SpecFlowFeature3 In order to test the login functionality for multiple users, we will demo using scneario outline Scenario Outline : Verify login for different set of users Given  User trys to login into application using  <Username>  and  ...
Read more

Specflow -Part6(Specflow Hooks)

Image
We may come across a scenario where we need to execute code after/before a particular event like given below We want to create some folder where we can store screenshots/ logfile before starting the test We may want to log details of the scenario in a log file after executing each step  We want to know after each step if that step was successful and if not we want to take a screenshot as an evidence We want to clean up the database before/after each scenario/feature  We  may want to open/close browser for every scenario Hooks help us to execute logic when a certain event occurs, let's check how I will start with creating a new project called SeleniumHooks and added folders where we can keep our feature, feature definitions and hooks file We will add a feature file and implement the steps Feature : SpecFlowFeature1 In order to avoid silly mistakes As a math idiot I want to be told th...
Read more