Continuous test automation is the key to ensuring success in the Agile software development. Also, it’s an essential skill for the most testing and QA job profiles. That’s why we brought the top automation testing interview questions to help test engineers in delivering their best during interviews.
All of these are the most asked questions while selecting a candidate for the automation job profile. We’ve even tailored the answers by discussing with the candidates who had success in their automation interviews.
We believe you would get the same benefit from this post as most of our readers have gained from reading the following most popular post on Selenium testing.
Before you proceed, do you wish to understand why is it important to learn test automation?
The concept of test automation is not new at all. However, it is the Agile model which replaced the traditional waterfall approach and made the automation testing necessary.
In Agile testing, software testers not only get to explore new ways of using automation but also have to make many thoughtful decisions. That’s why we’ve added different types of automation testing interview questions to help you even in your routine tasks.
Automation Testing Interview Questions.
- What are the criteria for selecting a test case for automation?
- Which types of test cases should you exclude from automation testing?
- What are the main stages in the automation testing lifecycle?
- Which are the main tasks during the planning phase of automation testing?
- What are the principal features of a good automation tool?
- What different approaches can you use for designing an automation solution?
- Which are the main tools for software automation testing?
- How do you measure the success of automation testing?
- Can automation testing fully replace manual testing?
- How do you plan automation testing of a web application?
- What are the Pros and Cons of doing automating testing at UI layer?
- Why would you want to automate a test?
- What is the recommended test automation strategy?
- Can you define an automation framework?
- What coding practices should you follow during automation?
Automation Testing Interview Questions & Answers.
Let’s begin with a few questions to build a basic understanding of automation. In this section, we’ll quiz you to justify the need for automation.
Ans. We recommend considering the following points for automating a test case.
- Determine the execution frequency of the test case. Do you run it often for every new build or once with large input?
- Find out if automating it would save you time that you can devote to exploratory testing.
- Is the test case critical for business or does it cover an end-to-end scenario?
- Make sure analyzing the result of an automated test should not exceed the time it used to take during manual execution. Otherwise, it’ll lose its viability for automation.
- Do consider the likelihood of the test catching defects.
- Could it be a blocker for a major feature or functionality which is critical to business? If the answer is yes, then make sure to it get automated and passed in every build.
Ans. This question is just the reverse of the previous one. In this, we’ll know how to filter the test case from being automated.
- Usability tests which require manual intervention to check for errors or deviation from expected behavior.
- Test cases which include setup and installation or cases which don’t need re-execution. However, you should automate tests which assume large input data.
- Avoid automating tests which could return unpredictable results. e.g. time-bound tests, expiry date verification.
- UX tests which involve verifying objects re-sizing on different screen sizes.
- Bar tests from automation that are intended for quick execution. Any such test should go through manual test execution. However, you can take note of those to be run regularly and automate later.
- Rule out any unplanned and random test cases from automation.
Ans. Following are the primary steps to carry out automation testing.
- Make a decision to commence automation.
- Identify and induct an Automation tool.
- Determine the scope of automation testing.
- Design and development of test suite.
- Continuous test execution (On demand or Nightly basis).
- Regular maintenance of test suite.
Ans. In the planning stage, a tester should execute the following tasks.
- Decide on the “right” automation tool.
- Choose an automation framework if required.
- Clarity on what to include and exclude from the test automation.
- Define milestones and share with stakeholders.
- Track progress using any project management tool like MPP.
- Test environment configuration.
- Identify Test Deliverables.
Ans. A good automation tool should have the following characteristics.
- Quick and easy test environment setup.
- Cross platform support.
- Good debugging/logging support.
- Robust object identification.
- Object and image testing abilities.
- Cross browser testing support.
- Database integration and validation.
- Should facilitate crowdsourcing.
Ans. We can design a test automation solution based on the following types of frameworks.
- Data-driven automation framework.
- Keyword-driven automation framework.
- Modular automation framework.
- Hybrid automation framework.
- Behavioral driven development framework.
Ans. Some of the most common automation testing tools are as follows.
- QTP (HP UFT),
- Rational Robot,
- Selenium Webdriver,
- Soap UI,
- Fitnesse, and
- Squish for QT.
Ans. Software test engineer or a QA manager can use the following indicators for tracking the success of automation testing.
- Automation testing coverage ratio.
- Code coverage level.
- Defect detection ratio.
- Reduction in the manual test cycle.
- Time to release the product.
- Reduction in labor & other costs.
Ans. Automation testing isn’t a replacement for manual testing. It’s just a continuation of the manual testing.
Because there are many situations where an automated solution can’t displace the insight, understanding, and experience of a tester.
Ans. We can plan the automation testing requirements of a web application in the following manner. You can adopt these rules irrespective of the automation tool like SilkTest, QTP, Selenium or any other test tool you are using for automation testing.
- Web UI testing.
- Every web page should have unique names.
- A similar type of objects should follow the uniform naming scheme.
- No object should have a duplicate name.
- The test must ensure that every image has its ALT attribute set.
- Dynamic content should have a proper name, ID or XPath.
- All tables displaying data should have names.
- Cross-browser consistency.
- Web service layer (Rest/Soap) testing.
- API Request/Response validation.
- API error code checking.
- Web service XSD verification.
- Cross-server (tomcat/web sphere) validation.
Ans. Automation testing when performed at UI layer could have both positive and negative impacts.
- Since UI automation simulates a real-time user, so it is useful for verifying end-to-end UI flows.
- It could help testing application integration with the external systems.
- The test suite can also be given to the customer to collect his feedback and gain confidence.
- Automation tests can provide early feedback on high priority modules and help to reveal severe bugs.
- Provides the ability to verify UI functionality even when it is not possible to test manually.
- UI automation can break when there are frequent changes in the UI element locators.
- Test execution is slow as UI actions use a delay in processing.
- Automation can verify only a limited information which is available.
- You need to cap the volume of test cases executed due to their slowness.
- Automating a UI test could be time intensive as it involves many steps.
Ans. There are several benefits or reasons to automate a test.
- Incremental test automation can lead to increase in test coverage.
- It uplifts the quality of the build produced.
- Testers can utilize the time saved in performing exploratory testing.
- Regression test suite can help in finding new bugs.
Ans. In the Agile process, the pyramid testing strategy is quite successful. It segregates automation tests into three levels and also caps the tests at each level.
At the first level comes the unit tests which own the largest chunk of tests and form the basis of the testing pyramid. Next level belongs to the service layer which includes API tests. Finally, comes the GUI tests which sit at the top of the pyramid.
Testers use them to validate the application as a whole. Each layer offers a test coverage level in proportion to the tests it executes. Running unit tests take less time and cover multiple permutations. However, they don’t verify the integration between the components. API tests fill this gap and validate how the units function together. But they also not factor in the end-to-end use cases. Here the UI tests take the ground by regressing multiple units in a single test. These tests tend to be fragile and could be very slow in execution. Hence, each layer has a significant role in the overall testing strategy. Please refer the image given below. It is depicting the different levels of automation testing pyramid.
Ans. An automation framework is a software platform which provides the necessary structure and echo system to automate and execute tests. The framework also puts up a set of guidelines for users to maintain and use it efficiently.
And you can even extend the framework using them. These guidelines are as follows.
- Rules for writing test cases.
- Coding guidelines for creating test handlers.
- Input test data template.
- Object repository management.
- Log configuration.
- Test result and reporting usage.
Ans. Some of the best coding practices that a tester should use are as follows.
- Create reusable test handlers and put them in a separate file.
- Don’t miss to add comments while adding a new feature or fixing a bug.
- All programming languages also have their respective standards. Try to follow them.
- Always use an external data source to store test data.
- Make a habit of running your test scripts on a regular basis.
Summary – Automation Testing Interview Questions for QAE.
There is no doubt that questions above could help you in cracking interviews. However, you can also use this knowledge in improving your testing skills.
If you have any query on the above automation testing interview questions, then do write to us. And if you’ve read this post through the end, then don’t miss to like it or share on social media.
All the Best,