Automation Interview Questions and Answers

Q1. Explain what is automation testing?

Ans: Automation Testing is a procedure which is performed with an automation tool to write and then implement tester’s test scripts and cases. The primary purpose of Automation Testing is to lessen the number of test cases to be run by hand and not disregard Manual Testing all in all.

Q2. When exactly you will automate a test?

Ans: There are certain cases when we can consider the same. For example, repeating tasks. During such a scenario, automating a test saves a lot of time as well as human efforts. In addition to this, test with more than one data set can be made more efficient through this approach. Also, regression test cases, as well as Smoke & Sanity tests are also the conditions when automating a test is a good option. However, the final decision is always based on Return-on-Investment.

Q3. What do you think about the normal advances that are engaged with Automation anywhere process?

Ans: The primary thing is to choose the test tool. After this, the following stage is to design the extent of automation anywhere took after by the means arranging, planning and improvement. Following stage is testing execution and the last advance is support. It is fundamental to take after the means in the characterized arrangement to remove disorder.

Q4. What criteria do you consider for automating a test?

Ans: I would consider the following points to help me decide if a test should be automated:

How often does the test need to be executed? i.e. is that going to be a regression test? Sometimes the test will need to be executed once, but with a large set of data

How much time does automating this test will save me so that I can use my time in exploratory testing

How important is the test to the business; i.e. is the test scenario a typical user journey through the application

How complex is it to automate the test and how likely is it that the complexity doesn’t cause many false positives which increases results analysis time?

How likely is it that this test catches a defect?

How likely is it that a feature or functionality will break and what is the impact of it to the business? If it is high impact, then it should be automated to ensure it passes from release to release

Q5. Does automation replace manual testing?

Ans: We cannot actually replace manual testing 100% using Automation but yes definitely it can replace almost 90% of the manual test efforts if the automation is done efficiently.

Q6. When is it not appropriate to automate testing?

Ans: One should not automate in following cases:

1.When the Application which has to undergo the Test changes regularly

2.Test cases that are to be done only once

3.Adhoc or Random testing

Tests that need to be verified visually

Q7. What do you know about the common steps that are involved in Automation anywhere process?

Ans: The very first thing is to select or consider the test tool. After this, the next step is to define the scope of automation anywhere followed by the steps planning, designing, as well as development. Next step is Testing execution and final step is maintenance. It is necessary to follow the steps in the defined sequence to eliminate confusion.

Q8. What are the basic components that must be dealt with while organizing Automation anyplace?

Ans: Before doing anything, the central thing to a center is picking the Automation tool that is important. It is fundamental to give the watchful design to the framework in case it is accessible. The test condition setup is close to essential to consider on require. Another factor that issues a considerable measure is aware the test output. Moreover, factors, for example, for example, the course of events of the undertaking and its execution are substitute factors that must be taken between the arranging stages.

Q9. Why would you want to automate a test? Is it to?

Ans: Increase test coverage?

• Improve quality?
• Save time for exploratory testing?
• Find more bugs?
• Replace manual testers?

Q10. How do you plan test automation?

Ans: Planning is the most important task in Test Automation. Test Automation Plan   should cover the following task items,

1. Tool Selection:  Type of Test Automation Expected (Regression / Performance etc.)
2. Tool Evaluation: Tool Availability / Tool License Availability / Tool License Limitations.
3. Tool Cost Estimation Vs Project Cost Estimation Statistics for Testing.
4. Resource Requirements Vs Availability Study.
5.  Time Availability Vs Time Estimations Calculations and Definitions.
6. Production Requirements Analysis Results Consideration with respect to Factors like Load-Performance / Functionality Expected / Scalability etc.
7. Test Automation Process Definitions including Standard to be followed while performing Test Automation.
8. Test Automation Scope Definition.

10. Automation Risk Analysis and planning to overcome if defined Risks Emerge in the Automation Process.
11. Reference Document Requirement as Perquisites for Test Automation.

Q11. What is the condition that is unsuitable for the use of automation testing for the Agile methodologies?

Ans:

• Automation testing is not a good option for agile methods in subsequent circumstances
• As soon as Agile testing asks for frequent changes in requirements
• When extensive level of papers is required in Agile
• It is only proper for those reversion tests during agile testing like uninterrupted integration

Q12. What are the automation tools you are certified in?

Ans: The answer to this question depends on you. You can mention here about the tools you have good command or skills in. Generally, it is asked from experienced professional in the Automation.

Q13. Can test automation improve test effectiveness?

Ans: Yes, Definitely Test Automation plays a vital role in improving Test Effectiveness in various ways like,

1. Reduction in Slippage caused due to human errors.
2. Object / Object Properties Level UI Verifications.
3. Virtual Load / Users usage in Load/Performance Testing wherein its not possible to use so many resources physically performing test and get so accurate results.
4. Précised Time Calculations.
5. And many more.

Q14. Name any five things which you can automate?

Ans: The following are the five things:

1. Smoke Sanity test suite
2. Smoke test suite
3. Automation behind GUI
4. Construct sending
5. Test information creation

Q15. What are Pros and Cons of automating tests at UI layer?

Ans: Pros

• UI automated tests execute in a way that simulates user interacting with the system. So it is very good for validating user journeys and flows
• Can cover end-to-end flows that communicate with 3rd party systems
• Because tests are run against the system, they can be demoed to the customer who can understand what tests are run
• Can catch high severity or show stopper bugs
• Can check UI functionality where it is not possible to test otherwise

Cons

• UI automated tests can be very brittle (i.e. fail due to UI changes even though functionality hasn’t changed)
• Slow feedback to the team. Execution is slow as you have to wait for the system to launch and connections with 3rd party system can take a long time
• Limitation on what can be checked from the UI. There are some information that are not present from the UI
• Because tests are slow from UI, we can’t have a lot of tests running against the UI
• Can be time consuming to construct automated test scripts for the UI
• Usually have to depend on a 3rd party tool or vendor for UI testing

Q16.List down the primary features of a good automation tool?

Ans:

• Test Environment backing
• Easy to use
• Decent repairing ability
• Healthy object identification
• Object and Image analysis aptitudes
• Object identification
• Ability to test database
• Should be able to upkeep multiple frameworks

Q17. What are the features you would look while selecting a tool for automation anywhere?

Ans: The tools must be easy to use and have test environment support available simply. It must have debugging ability for the smooth operations. It is quite true that testing image and objects are the important aspects in the Automation Anywhere. Therefore, it must have a better image and object testing ability. Also, it must be capable to test the database. Object identification, as well as multiple framework support, are the other features that must be there in a tool for Automation Anywhere.

Q18. What are the main attributes of test automation?

Ans: Here are some of the attributes of test automation that can be measured,

Maintainability

• Definition: The effort needed to update the test automation suites for each new release.
• Possible measurements: The possible measurements can be e.g. the average work effort in hours to update a test suite.

Reliability

• Definition: The accuracy and repeatability of your test automation.
• Possible measurements: Number of times a test failed due to defects in the tests or in the test scripts.

Flexibility

• Definition: The ease of working with all the different kinds of automation test ware.
• Possible measurements: The time and effort needed to identify, locate, restore, combine and execute the different test automation test ware.

Efficiency

• Definition: The total cost related to the effort needed for the automation.
• Possible measurements: Monitoring over time the total cost of automated testing, i.e. resources, material, etc.

Portability

• Definition: The ability of the automated test to run on different environments.
• Possible measurements: The effort and time needed to set-up and run test automation in a new environment.

Robustness

• Definition: The effectiveness of automation on an unstable or rapidly changing system.
• Possible measurements: Number of tests failed due to unexpected events.

Usability

• Definition: The extent to which automation can be used by different types of users (Developers, non-technical people or other users etc.,)
• Possible measurements: The time needed to train users to become confident and productive with test automation.

Q19. Which factors are necessary to evaluate for scripting standard for Automation Anywhere Testing?

Ans:

• For every ten lines of code, there ought to be three lines of code
• Most extreme utilization of system wherever possible is likewise a vital factor.
• Proper space, Uniform naming tradition, Error dealing with and administration.

Q20. What are the various kinds of the frameworks that can be used in software automation testing?

Ans: In software automation testing four kinds of frameworks are usually used

• Keyword driven automation framework
• Data-driven automation framework
• Hybrid automation framework
• Modular automation framework

Q21. Name any two important tools for Automation anywhere testing?

Ans: There are several tools but the ones that are considered as best are Rational Robot and QTP. Both of them are equally powerful and help to get results that are totally error free.

Q22. How will you choose a tool for test automation?

Ans: Below are factors to be considered while choosing Test Automation Tool,

1. Test Type Expected. (E.g. Regression Testing / Functional Testing / Performance-Load Testing)
2. Tool Cost Vs Project Testing Budget Estimation.
3. Protocol Support by Tool Vs. Application Designed Protocol.
4.  Tools Limitations Vs Application Test Requirements
5. H/W, S/W & Platform Support of Tool Vs Application test Scope for these attributes.
6. Tool License Limitations / Availability Vs Test Requirements.(Tools Scalability)

Q23. What are the purposes of not considering manual testing in automation anywhere approach?

Ans: The best issue is it needs a huge measure of extra assets and furthermore it's an endless procedure if done physically. There are sure odds of stacks that can announce their quality because of failure. At the point when ventures are time exact or when they are to an extraordinary degree sweeping, surely noticeable, it's not an intelligent alternative to consider manual testing. It can corrupt the execution of advantages performing testing because of losing interest by playing out a similar assignment over and over in a brief span cross.

Q24. What is Depth Testing?

Ans: A test that workouts a specific feature of a product in complete detail.

Q25. What do you know about the type of framework that is used in Automation anywhere software?

Ans: There are four important frameworks that are commonly used. First is Keyword Driven Automation Framework. Next is Data-driven automation framework. The third is Hybrid Automation Framework and last is Modular automation framework.

Q26. Describe common problems of test automation.

Ans: In Test Automation we come across several problems, out of which I would like to highlight few as given below,

1. Automation Script Maintenance, which becomes tough if product gets through frequent changes.
2. Automation Tool’s Limitations for objects Recognizing.
3. Automation Tool’s Third Part Integration Limitations.
4. Automation Tool’s abnormal behavior due to its Scalability Issues.
5. Due to Tool’s Defects, We might assume its Application Defect and consider any issue as Application Bug.
6. Environmental Settings and API’s / Addins Required by Tool to make it compatible to work with Specialized Environments like JAVA-CORBA creates JAVA Environmental Issues for the Application to work. (E.g. WinRunner 7.05 Java-Support Environmental Variables Creates Application Under Test to malfunction)
7. There are many issues, which we come across while actual automation.

Q27. What do you think about the sort of structure that is utilized as a part of Automation anywhere programming?

Ans: There are four critical structures that are usually utilized:

• Watchword Driven Automation Framework.
• Information-driven automation system.
• Crossover Automation Framework
• Particular automation structure.

Q28. What is Dynamic Testing?

Ans: Testing software through implementing it.

Q29. What do you mean by QTP?

Ans: It stands for Quick test professional and is basically an Automation tool that is considered in test environments.

Q30. Explain How QTP Identifies Objects?

Ans: For each object class that QTP identifies, it has a set of properties stored. These include mandatory properties, which is essentially a description of any given object, which checks if it’s a child or parent object as well. Next are the assertive properties, which QTP resorts to only if the mandatory properties are insufficient at identifying the object. If all else fails, QTP resorts, finally, to its ordinal identifier.