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 PhantomJS

PhantomJS can be termed as yet another powerful tool for testing. It supports varied web standards and it is developed with JavaScript API which permits webpage capturing, pages manipulation, access to file system and page settings.

Selenium Webdriver is an open source automation tool and definitely a great JavaScript automated testing framework which supports all operating systems and browsers such as Mozilla, Safari, Firefox, and IE. In addition, it runs multiple tests and supports programming languages such as Java, C#, Ruby, PHP, Perl and Python.

The goal of PhantomJS is different than Selenium Webdriver . The purpose of running tests with PhantomJS is to quickly identify the first possible problems, much like exploratory testing. Imagine if the web application is a web-based email client and QA Tester mistakenly break the sign in screen. It would save a lot of time if such sign in problem can be detected as early as possible before launching the extensive mail functionalities tests in a variety of web browsers.

This particular objective is achievable because PhantomJS can run quite well on the command-line and it has near-zero dependencies. It fits nicely during the development workflow, e.g. as part of git precommit hook, and also the initial testing stage in the build/continuous integration server. Since the latest PhantomJS already includes built-in support for WebDriver, it is also possible to run the exact same tests both with PhantomJS and with the typical WebDriver environment.

Selenium simply automates web browsers. PhantomJS is a headless browser that could be used to speed run the automated tests developed using either Selenium IDE or WebDriver. Execution speed is the key in PhantomJS.

Selenium is basically a suite of tools that are required for automating web browsers across multiple platforms. Packaged with the support of leading browser vendors, Selenium is being regarded as the core technology that’s used in an unlimited number of APIs, automation tools and frameworks.

Selenium Webdriver can be controlled by multiple programming languages and testing frameworks, it runs in multiple browsers and operating systems. Selenium permits an automated control of real browsers on real operating systems, thereby ensuring that the tests are too close to real user experience. Keep in mind Selenium bindings can be used for controlling PhantomJS, covering over ninety of the testing requirements. For extra powerful testing, Selenium permits QA Tester to set up additional browser connections without the need for altering even a single line of code.

Selenium vs PhantomJS conclusion:

PhantomJS and Selenium are two of the best JavaScript testing tools presently used by QA Tester. They are perfect in their roles, understanding their unique capabilities would help you decide which one to choose. If your intention is to execute multiple tests within a short period of time, then using PhantomJS would be a feasible option because with Selenium, it could be a time-consuming process. Another great advantage with PhantomJS is that as it is backed by command-line based usage, the JavaScript code of the website is sandboxed and not left on the screen. Therefore, it doesn’t interact with the principal tool.

On the other hand, PhantomJS wouldn’t be a good choice for web app testers as it serves as a single version of WebKit. In short if you prefer to use headless browsers for testing, QA Tester can choose either Selenium or PhantomJS, depending on your requirements. There is no superior framework. It depends on the QA Tester.

No comments: