Interfaces and Abstract class

-
Interfaces

 An Interface contains definitions for a group of related functionalities that a class can implement. Interfaces are contracts that your class should abide by.

 Requirement

 Suppose you are creating a Web Automation tool, that targets IE and FF browser and supports the functionality of Opening and Closing the browser.

Here you can notice that the functionalities will remain the same for both the browsers and also other new browsers which you can support in the future.

We can have individual classes implementing these functionalities for respective browsers however we want all the classes to implement the functionalities(Opening and Closing Browser) which we defined earlier.

So how can we force the class to implement the functionalities or contracts which we defined?

Well that's where interfaces help 

 We can define an interface or contract with all our requirements and let other browser classes provide their implementations for those functionalities































Here IE class implements WebAutoTool interface, you can do this for FF class.

Point to note here is we are creating an instance of IE class and storing in WebAutoTool interface variable

WebAutoTool webAutoTool = new IE();

This satifies one of the design principles which states as "Program to interfaces rather than concrete class"

 Once you depend on interfaces than you are decoupled from the implementation and it can vary which should not bother you.

In our above code, we are free to pass a webAutoTool object across the solution and we don't care whether that's an IE, FF or any other browser instance.

Also if we are going to decide our browser at runtime than programming to interfaces helps
All in all, an interface acts as insulation from the implementation details 👱

Abstract Class

 We will stick to our earlier example of Web Automation tool, here we assume say opening, closing and some more functionalities of the browsers share the same code.
So if we are using interfaces here then we will be writing the same code for those functionalities.

Wouldnt it be great if I can add some implementation inside interface and that could be shared across the browser classes?

Well, interfaces cannot contain implementation code. So what next ?

Abstract classes can achieve above requirement, they may contain implementation code.
They are special classes which cannot be instantiated however other classes can inherit from an abstract class.



































Here we defined abstract class WebAutoTool and added implementation for Open and Close methods which can be shared across all browser classes.

We defined another method called Sendkeys and added keyword abstract to it , it means child class can add their implementation for this method

We added child class IE and inherited it from WebAutTool class , we also override the implementation of the SendKeys method.

Well that's it, now we will look at some differences between abstract class and interfaces

  1. An abstract class may contain implementation code, interfaces cannot.
  2. A class can inherit from a single abstract class however it can implement multiple interfaces
  3. Abstract class members can contain access modifiers however in case of interfaces members are automatically public
  4. An abstract class can contain anything similar to concrete class however interfaces can only contain methods, properties, events and indexes, and no constructor/destructor etc.
Important points

When you add a new method to an interface than you can break all your client code.

 The interface gives freedom with regard to base class and an abstract class gives you the freedom to add new methods later







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   | |  101        |  Jon          |  Medical      |  40   | |  102        |  Steve        |  Engineering  |  50   | Then  I print details on console Custom Class public   class   Student     {         public   int   StudentId ;         public   string   StudentName ;         public   string   Division ;         public   int   Age ;
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  <Password> When  User enters the  <Username>  and  <Password> Then  User should be successfully logged as  <Role> Examples :  |  Username   |  
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 the sum of two numbers @mytag Scenario : Add two numbers Given  I have entered 
Read more