Explore topic-wise InterviewSolutions in .

Over the years, many automated tools have COME up and they have helped immensely in the overall process of automation testing. Some of the most popular tools include Selenium, RANOREX, APPIUM, UFT, Tosca and SoapUI.

Yes. Documentation is essentially required for QA automation. All the different methods and procedures that are going to be employed must be documented REALLY well in order to repeat them the next time once again. CRUCIAL things that need to be documented are designs, CODE changes, test specifications, CONFIGURATIONS, bug reports and various other aspects. When you document them, you can keep track of the results and repeat them for the next process.

Automated TESTING was never the replacement for manual testing. It was introduced to help and to be an alternative for manual testing. No matter how much easier and efficient it is, this kind of testing also has its own limitations. That is why you will ALWAYS need the help of manual testing in software development. Both automated and manual testing have their own pros & CONS which needs to be kept in MIND. Automated testing can never help you get an in-depth analysis of many aspects. On the other hand, manual testing can never be so efficient.

There are some different conditions in which you cannot consider automated testing. These are the conditions REQUIRED for QA automation.

• Exhaustive documentation
• Single USE TEST cases
• Ad-hoc testing
• Exploratory testing
• User interface testing
• Ever changing resources

You have to KEEP in mind that it is NEVER possible to achieve 100% automation. This is because there are MANY test cases which can't be automated so easily. In those cases, it takes more time to write the automated test than it is going to ACTUALLY save. Investing double the time and EFFORT in order to make things automated, is not worth it. Manual testing is the best in such cases where you cannot use automated testing because of such reasons.

Not every automated testing process can be SUCCESSFUL. There are always exceptions. TAKE a look at these factors which will help you to determine the success of AUTOMATION -

• Time saved
• Total number of defects found
• TEST coverage
• Maintenance Time
• Cost of installment
• Test re-usability
• Quality of software under the test

Before you start an automation testing, there are a few pre-requisites that you NEED. Without them it will be difficult to execute the process. Here are the pre-requisites required for QA automation you will need -

• Good framework build which needs to be stable at all times
• You have to use reusable functions and PROCEDURES during the process
• Carefully store all different reusable functions in separate files
• You have to filter and separate the TEST cases that needs to be automated
• Ensure that the modules don't change very frequently during the process
• Skilled and premium resources

There are a few GOOD practices which you can follow when you are writing a test case. FOLLOWING these practices help to ease the overall PROCESS and allows the system to function EFFICIENTLY. Some of these good practices essentially are as follows -

• To use comments appropriately
• Maintain files for reusable functions
• Follow good coding conventions
• Run different scripts regularly

Lot of people get CONFUSED regarding what an automated test script is. This is basically a short PROGRAM which gets written on any programming language in order to perform a certain set of instructions. The automated test scripts help to VERIFY if an APPLICATION runs as per the preferred requirements or not. When you RUN the script, it will give you a pass or fail result based on how the script has performed.