Q1: What is automation testing?

Ans: Automation testing is a software testing technique in which a tester performs the tests programmatically using a tool or framework rather than manually going through the test cases and running them one by one. The fundamental aim of automated testing is to save time, effort, and money on repeated, infrequently changing tests.

Automation testing assists teams and organizations in automating testing operations, minimizing the need for human involvement and attaining higher speed, reliability, and efficiency. It also helps to shorten the development cycle since engineers receive immediate feedback and may iterate rapidly.

Q2: What’s the difference between manual testing and automated testing?

Manual Testing

• The test cases are executed one by one by a person, with no software help.
• Effective for non-repeatable tests that need human inventiveness, involvement, and subject knowledge.
• Good for accessibility and usability testing since the tester can evaluate the programme from an end user's standpoint.
• It can be sluggish and time-consuming, as well as prone to human mistakes and misjudgment.
• Randomized testing, often known as exploratory testing, is an option for testing software.
• A human tester can readily detect UI issues and inconsistencies.
• It is extremely difficult, if not impossible, to do performance testing on software under severe stress.
• Prior programming expertise is not required of the tester.

Automated Testing

• Without human intervention, tests are run by a testing tool or framework.
• Appropriate for repeated testing where the software functionality under test does not change frequently.
• Useful for testing regression problems to ensure that the programme does not break after making new modifications.
• Because a machine conducts them, automated tests are quick and error-free, as long as we test the correct item.
• Automated testing does not allow for exploratory testing.
• Unless it is configured to do so, automated testing cannot detect and report UI issues.
• Automation testing makes performance testing simple.

Q3: How do you choose a tool/framework for automated testing?

Ans: You must rely on software tools or frameworks to do any automated testing. There are several possibilities from which to select. Here are some factors to consider while evaluating these tools.

• Programmable (code-based) or code-less tools. Some tools need programming knowledge, while others do not, allowing a non-coder tester to construct test cases with visual aid. It would help if you made your selection based on your team's expertise and skill set.
• Commercial vs Open Source. The cost of the tools varies greatly depending on the features they contain. Commercial products might be costly, but you receive tech assistance when you need it. Although open-source software is free, you must conduct a study when resolving issues.
• Ease of use. Some automated testing technologies are notoriously difficult to use and need significant training before providing any benefit. Some are simple to use and may be used right away.

Selenium, Katalon Studio, UFT, TestComplete, Testim, and others are among the most popular automation tools. Consider the testing needs for your project, contact your team, and analyze their skills, expertise, and familiarity with the tool when selecting one. You should also evaluate the tool's return on investment regularly and be prepared to switch if necessary.

Q4: What is a test environment?

Ans: A test environment is a computer or a server where software is tested. After the team completes the software development, the tester instals it on this machine and all of its dependencies in the same manner as the production environment. It enables the tester to put the programme through its paces in a real-world setting. A test environment enables the tester to establish consistent test settings whenever a new version of the programme is published. The test environment comprises the testbed, the test data on which the tester will test the programme. This information assists the tester in invalidating test scenarios that need a specific configuration. The test environment is often a carbon replica of the production environment. Having a duplicate copy helps the tester consistently recreate the issues identified by customers and give the developers the exact procedures to repair them.

Q5: What is the Robot framework? Please provide a brief overview of its architecture.

Ans: Robot Framework is a growing open-source automation testing framework mostly used for robotic process automation (RPA). The goal of robotic process automation is to mimic human activities and interactions using the software. Robotic automation, like actual people, can grasp (to some extent) what is on the screen, press keys and buttons, browse to links, and retrieve data.

The Robot Framework is built in Python and is platform-independent. The majority of the libraries in the ecosystem are open-source as well. It features a modular architecture that may expand with additional libraries. It stores the test data in files and uses a framework-specific syntax to do so. A test suite comprises several such tests.

When you start the tests, the Robot Framework parses the test data and interacts with the programme using the keywords given by the libraries. These libraries interact with the programme either directly or indirectly via driver tools.

The test is conducted from the command line by the Robot Framework. However, full reports and logs are available in both XML and HTML forms. The framework provides strong out-of-the-box support for standard libraries such as ArchiveLibrary, BrowserLibrary, DataDriverLibrary, HttpRequestLibrary (for Java), and so on.