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 2 WebDriver Interview Question - WebDriver best practices

Best practices in interviewing Selenium QA Tester obviously include the questions about Selenium best practices for web application testing. For example QA Manager could ask about best practices fort creating Selenium WebDriver instances. Should all test cases use a single WebDriver instance or should every test case create a new WebDriver instance?

Selenium QA Tester with a practical experience most likely would answer that reusing WebDriver instances between test case will save time when using ChromeDriver, InternetExplorerDriver, FirefoxDriver, OperaDriver drivers, but provides almost no time benefits for HtmlUnitDriver. In the same time one of the testing goals is to have reproducible tests and keeping WebDriver running between test cases may provide side-effects. The recommendation would be to create a new WebDriver instance for every test execution. In this case each test case would be executed independently from any other test case.

No comments: