Here QA Tester can find Selenium interview questions with examples. I started to put together and continuously update interview question for Selenium WebDriver test automation tool. This Interview questions were asked during real QA interviews for Selenium QA Automation Engineer position in the leading companies. I believe that any QA Engineer, no matter seasoned one or novice one, would greatly benefits from this collection Selenium interview questions and tips. If you are plan to attend an interview you need to know the answers on these questions by heart. I provided answers on several technical interview questions, but you have to think how you would personally answer these questions. Finally, I would ask anyone of you to provide answers on unanswered Selenium interview question, so we all would benefit from this knowledge sharing and it would help us to land on Selenium QA Automation Engineer job and work successfully. If you were asked the interview question that is not in the list, post it with your answer.

Selenium vs Protractor

Selenium or Protractor? What is better for testing a web application? Experienced QA Engineer could meet this Selenium interview questions quite often. QA Tester with 5 years of experience may propose Selenium for a web application rather than Protractor, while QA Engineer with no experience would prefer to automate the testing with Protractor and ditch Selenium. Who is right? Let’s answer on this QA interview question starting with definitions to avoid opinion-based solution:

Selenium is an open source suite of tools to automate web browsers across many platforms.

Protractor is an end-to-end open source test framework for AngularJS applications.

Selenium is considered one of the greatest test automation framework used for testing complex web based applications. Protractor is designed for applications built in AngularJS. While there is some support for using Protractor with non-angular web applications, test engineer would lose the awesome async functionality of Protractor while testing non-angular web applications

Technically speaking software engineer cannot compare Selenium vs Protractor, because software engineer cannot compare suite of tools with framework. It like comparing apples and pumpkins. So the summary would be the following:

Selenium works great for testing AngularJS, the only problem is dealing with synchronization issues.
Selenium is in fact a de facto tool in the open source market for browser automation.
QA Engineer can work with Selenium in almost every popular language.

Protractor Is marketed as AngularJS based automation tool but when you will look at its core its
wrapper for WebDriverJS.
Protractor has great advantage in case of AngularJS specific locator strategy and the tool provides more option to work with AngularJS directives
Protractor is only available for only one language, so to work with QA Engineer must know JavaScript.
Protractor is a new tool in the web testing market although based based on the WebDriverJS.

The correct answer on this QA interview question would be that Selenium or Protractor answer is totally depends upon the project requirement, team knowledge and management preferences. If your application is not built on top of angular, you can use webdriver on top of any other languages you prefer. It will not be smart to declare which has what advantage over other, both tool are great and help test engineer to make browser automation flawless and web sites more reliable.

No comments: