I will be discussing about what is authentication, why we need authentication in APIs, what are the different authentication mechanism and the misconception of authentication vs authorization.
This is the second article in the series and if you didn’t checkout the first feel free to have a look.
In simple terms, authentication is used to identify the entity trying to access the resource. It could be a human or a machine. An ideal example from our day to day life is the finger prints you leave to open up doors in your office, Or the RFIDs tapped at each door…
Do your logs provide sufficient information for you to make great decisions? Do you add add log lines manually for every action you perform?
This might come handy for your selenium framework to provide you with more information.
WebDriver listeners, yes they are like CCTVs 😂 but little better, they capture only what they were asked.
Let’s check the implementation.
There is a class in selenium as “EventFiringWebDriver”, you need to create an object of EventFiringWebDriver.
Tip — If you have an existing implementation that returns a Webdriver, you can fix it easily returning EventFiringWebDriver instead of WebDriver.
I am planning to discuss the technical implementation and the usage of the webdrivermanager in this article.
I have written an Intro article on webdrivermanager, including the current status of the project. Highly recommended to read it before this.
First let’s take a look at how to use this in our project.
You can initialize the webdriver using three different ways provided by the webdrivermanager.
Web driver manager will take care of managing all your drivers. Interesting! isn’t it? Alright let’s dig deep with a cup of coffee.
Look at your automation test suite. Deep at the bottom, it is filled with various driver initialization methods. More browsers you support, more methods you implement at the base of your automation suite to power different browsers.
Not only that, you need to attach the respective driver binary file somewhere accessible by the code.
And the list keeps growing with your client requirement.
Here is your rescuer…
As the name suggests, smallest units of the software are tested and is acting as the safety net for any code level change.
Mostly done by developers and ideally use tools to automate.
According to the test pyramid, unit tests should occupy largely outnumber compared to any other test type. Hence this is the baseline of testing done on a product and is very powerful. Unit Testing will help to detect issues very early stages of the SDLC.
In our inventory control example,
Everything is constantly evolving and technology world is at it’s top. Hence no doubt about the role of a quality assurance engineer. The best way to grasp this is by looking at few job descriptions advertised by different companies around the world.
Web has been serving us for bit over three decades and it has evolved in many different ways. So far we have had 3 generations of web as Web 1.0, Web 2.0 and Web 3.0. Let’s have a look on what we had in each generations and technologies powered the web in each generation and the future.
This is the consumer content generation of the web where few people used to generate content and most of the people were consumers. Personal web pages were common and they served static content. …
This is for you !!!
You are not the only one, there is plenty that have gone, going and will be going though that hassle. Welcome to the club 🍺 !!!
Planning is the key and below are few points that will come handy. Truth is there is no easy way.
Plan to execute your test bed in parallel — this will definitely make your life far difficult yet in the longer run this would come handy. A test bed that will take 4–5 hrs of sequential run will definitely cut down some time for you.
Rely on a user…