automation testing interview questions

Automation Testing Interview Questions

Last updated on

Do you have an important automation testing interview? Are you also worried about the questions asked? Then do not fret. We have curated the top 50 frequently asked automation testing interview questions. These are quick 20 min read questions that will help you and prep you to crack the interview.

1. What is automation?

Automation is a method of running repetitive tasks, with minimum or about zero human assistance. This process is adopted to reduce human efforts.

2. What is automation testing?

Automation testing is using automation tools to create and execute test cases. It helps in finding defects and testing the overall working of the software. In automation testing, the test results are also generated automatically without the need for human intervention.

3. What is the need for automation testing?

Automation testing is important as-

  • It reduces human work/effort.
  • It saves from boring and tiresome monotonous work.
  • No need to create new test cases each time software is to be tested.
  • Fewer chances of error.
  • Speeds up the process of testing.
  • Reduces the cost of testing.
  • Easier to maintain test cases of lengthy and large applications or projects.
  • When manual testing becomes impossible.

4. What types of test cases should be automated?

Usually, we automate only those test cases that are repetitive, time-consuming, and critical to the application’s functionality. Below are some examples of the types of test cases that are good candidates for automation-

  1. Regression Testing: It is a type of testing in which the tester ensures that changes to the codebase do not adversely affect existing working functionality. Regression testing can be automated, and it is usually done after every code change.
  2. Smoke Testing: This is a type of testing that checks whether the application is stable and ready for further testing. Smoke testing is a preliminary test that is performed before starting any in-depth testing. If the smoke tests are automated then testers can quickly decide if the application is good enough to be carried out for in-depth testing, based on the smoke test results.
  3. Functional Testing: In functional testing the tester checks the functionality of the application, ensuring that it meets its business requirements. Functional tests that are repetitive should be automated to save time.
  4. Performance Testing: It is a type of testing that checks the application’s behavior under an expected or heavy load. Since performance testing involves virtual user generation should it can only be automated, to be carried out effectively.
  5. Integration Testing: It is a type of testing that checks how different modules or components of the application work together. Integration testing can only be automated as it checks the communication and interfacing between different modules.
  6. Security Testing: Security testing is a type of testing that checks the application’s security, ensuring that it is protected against common security vulnerabilities.

5. How to decide if automation testing is required?

The automation testing is required if-

6. Is complete 100% automation possible?

There are cases when the webpage might have a captcha. Or, there are test cases that are run seldom so automating such cases won’t bring any advantage. Therefore, having 100% automation is not possible.

7. During what circumstances automation is not feasible?

Automation testing is not feasible-

  • During random testing.
  • When the project is small and can be handled manually.
  • When the application under test is dynamic i.e. changes frequently.

8. What are the steps involved in automation testing?

The steps involved are-

  • Selection of appropriate test tool.
  • Planning and design
  • Test execution
  • Maintenance

9. What are the prerequisites before starting an automation project?

Some of the things to keep handy or have pre-requisite knowledge of are-

  • The Software Requirement specification document.
  • Choosing an appropriate tool for the testing phase.
  • Selection of framework(if required).
  • Deciding the type of test environment required.
  • Listing the test deliverables.
  • Preparation of a Gantt chart to keep the progress in check according to the timeline.

10. Are you aware of any common automation tools?

Yes. Some of the commonly used tools are Selenium, Jmeter, SilkTest, Load Runner, QTP, and Win Runner.

11. How does one decide which automation tool is appropriate for their project?

Things to be considered to select a tool for any project are-

  • Should support the application and technology you are working on.
  • Accessibility
  • Fits the cost and budget
  • Availability of extra support like tutorials and videos.
  • Easy to use
  • Debugging facility
  • Features to test the database
  • Support for multiple frameworks

12. What is the difference between automation testing and manual testing?

In Manual testing, the test cases are written as well as executed by the tester itself. In Automation testing, specific automation tools are used to run the test scripts. This makes the testing process easier and faster.

You can also read our detailed article here.

13. What is a framework?

A framework is a set of rules or guidelines. These are followed to create a versatile, robust, and effective test suite (in case of automation).

14. What is the use of the framework?

Different files and tools are required during automation. A framework is a mix of practices and tools to ease automation. All of this is kept in an organized manner by the framework itself.

15. Is automation testing impossible without a framework?

We can do automation without a framework. But a good framework helps in creating a robust and standard way of writing scripts.

16. What are the different types of frameworks?

Different types of frameworks are-

  • Hybrid testing framework
  • Keyword-driven testing framework
  • Data-driven testing framework
  • Module-based testing framework
  • Library architecture testing framework

17. What is a general structure of a framework?

A framework depends from project to project. However, a general structure would include-

  1. A source folder with test scripts
  2. A library folder consisting of libraries
  3. A class folder consisting of the class name
  4. Log folder having log files
  5. A file with URL, environment, and login information

18. What attributes declare a framework a good framework?

A good framework will be-

  1. Reusable – Methods written in a common file must be accessible to all the test scripts.
  2. Independent – This means if one test case fails it should not affect the rest of the test cases.
  3. Continuous – The test suite should be continuous or consistent.
  4. Modular – The framework should be flexible enough to adapt to changes.
  5. Reporting – This feature of the framework will mail our results and reports once the scripting is complete.

19. Why are URLs, logins, and, passwords kept in a separate file and not in the code?

These are very frequently used information. Thus if embedded in the code, we will have to keep updating them for each file they are referred to.

20. What are the reasons one will refrain from automation testing?

Some of the common disadvantages of automation testing are-

  1. Might prove expensive. The cost of automation tools is quite high.
  2. Testing of UI or UX of the application is difficult.
  3. It takes a lot of time to write exhaustive test scripts.
  4. Requires a team of professionally trained and skilled engineers.

21. What are some of the advantages of automation testing?

Some of the advantages of automation testing are-

  1. Increases the scope of test coverage.
  2. The requirement for resources is far less than in manual testing.
  3. It is more reliable.
  4. Execution of test cases way faster and more accurately.
  5. The team saves time for other levels in SDLC.
  6. More time to market the product.
  7. Reduction in maintenance cost.
  8. Improved product quality.

22. What will be your approach to testing a web application?

Whatever the application is it is important to choose the right automation tool. After this follow the following steps-

  1. UI testing of the website.
  2. The unique naming scheme for each web page.
  3. Grouping names for similar objects.
  4. Dynamic content should have an Xpath or ID.
  5. Cross-browser stability.
  6. Images should have the ALT attribute set.

23. What would be the automation strategy for agile software?

Some of the steps for effective automation will be

  1. Conduct parallel testing.
  2. Create quality test cases.
  3. Adopt DevOps integration.
  4. Choose the automation tool wisely.
  5. Cross-browser testing and cross-platform testing.
  6. Monitor the test environment regularly.

24. What will be your approach to automate a simple registration page?

To test the basic functionality of a registration page-

  1. Verify the requirements i.e. username field, password field, and a register button.
  2. Verify the UI of the page.
  3. Automating test case scenarios like-
    • The fields should not be blank.
    • Login should be possible with the registered email id and password.
    • Do not accept invalid email id or passwords.
  4. Prepare data input according to the test scenarios.
  5. Run the test suite and report bugs, if any.

25. What is a test script?

An automated test script is a short program written in any coding language to automate applications under test according to it. This program is then run. After that, the script itself marks the test cases as pass or fail based on the test logic.

26. What coding practices should one follow while automation?

Some of the good practices that one should follow while scripting are-

  • There should be a proper indentation.
  • At least 3 lines of comments for every 10 lines of code you write.
  • The naming convention should be uniform.
  • Maintain the test data systematically in different files.
  • Run your codes regularly.
  • The code should be robust enough to handle errors and recovery scenarios.

Conclusion

We have curated these questions independent of any specific coding language or automation tool. However, if you are to appear for an interview as an automation engineer, you should be well-prepared with at least one coding language. At the same time, have hands-on experience with any automation tool. This will help you gain more brownie points. Keep learning!

These automation testing interview questions are compiled by ArtOfTesting team member – Kanika Rawat. She is a tech enthusiast and loves coding.

Leave a Comment