1.0 Introduction

One of the product companies is looking to automate the regression Test Suite. During the discussion, they questioned why not all the identified Test cases can be automated. We responded that we have to do a feasibility study to identify that qualify for Test Automation and those who do not qualify. We explained that the objective of Test Automation is to reduce the cost of Testing. A feasibility study is critical to achieving a better Return on Investment. Sometimes overdoing Test Automation haunts us. It is very critical to identify the ideal Test Cased for Automation. This article would help to understand the factors that help to identify if the test case qualifies for Test Automation

2.0 Ideal Test Cases for Automation

A feasibility study is required to identify the test cases which can be automated. Tests

that require constant human intervention are usually not worth the investment to

automate.

The following are examples of criteria that can be used to identify tests that are prime

candidates for automation:

• High Path Frequency – Automated testing can be used to verify the performance of

application paths that are used with a high degree of frequency when the software is

running in full production. Examples include: creating customer records, invoicing and

other high volume activities where software failures would occur frequently.

• Critical Business Processes – In many situations, software applications can literally

define or control the core of a company’s business. If the application fails, the company

can face extreme disruptions in critical operations. Mission-critical processes are prime

candidates for automated testing. Examples include: financial month-end

closings, production planning, sales order entry and other core activities. Any

application with a high-degree of risk associated with a failure is a good candidate

for test automation.

• Repetitive Testing – If a testing procedure can be reused many times, it is also a prime

candidate for automation. For example, common outline files can be created to establish

a testing session, close a testing session and apply testing values. These automated

modules can be used again and again without having to rebuild the test scripts. This

modular approach saves time and money when compared to creating a new end-to-end

script for each and every test.

Applications with a Long Life Span – If an application is planned to be in production for

a long period of time, the greater the benefits are from automation.

• Compatibility Testing – If a test procedure is created for execution of compatibility

testing on various platforms and browsers, it‘s also a prime candidate for automation.

• Volume of Data – If a particular Test Case to be executed for different sets of data and that is also prime candidate for automation

3.0 Not All Test Cases qualify for Automation

There are several factors that determine whether test cases are qualified for automation or not.

Please find below some of the Parameters:

3.1 Test that needs to run ASAP.

• Tests that require ad hoc/random testing based on domain or subject matter expertise/knowledge. Tests without predictable results. For automation validation to be successful, it needs to have predictable results in order to produce pass-and-fail conditions.
• If a test needs to be manually “eyeballed” to determine whether the results are correct.
• Test that adds no value.
• Test that doesn’t focus on the risk areas of your application.

3.2 Types of Test Cases Not to Be Automated

3.2.1. Subjective Validation:

Subject validation protects the validity of words, statements, or initials. This also covers inspection and perceive testing. This is the stage where humans can quickly detect and provide feedback rather than the automated system that requires plenty of steps to write. So this type of testing is appreciated manually.

3.2.2 New Functionalities:

Performing automated testing for applications that are under development is not a good technique. It will cost a lot of time and resources to keep the automation tests updated and maintained. Automation testing will frequently fail and need to update regularly due to the changes in applications according to new requirements.

3.2.3. Strategic Development:

Certain applications require specific attention and subject matter expertise. Manual testing is suitable for these types of testing rather than automated testing.

For example, if there are business functions that needed special attention, the tester should focus on those areas with more focus and attention. Detailed test cases should follow covering every aspect. This usually covers the most critical part of the application.

3.2.4. User Experience:

Primarily, the success or negligence of an application depends on its usefulness. When there is a matter of user experience then nothing can compete with the human eye. It can detect any problem in seconds by looking at a picture like language, resolution, endurance, and formatting, etc. While automated testing will require a huge amount of time. So, it is suggested to leave the user experience property of any system to the human eye rather than an automated system.

3.2.5. Complex Functionality:

Some modules have complex functionality that an automated system cannot perform effectively. So, it’s better to automate those manually like in the case of Mobile device testing. Mobile device testing requires testing by leaving and reconnecting Wi-Fi, Run apps simultaneously, device authorization, and receiving and making phone calls.

3.2.6. Quality Control:

If the overall quality of the finalized application needs to be tested, then it is preferred manually rather than automatically. Automation testing can only test specific output that is generated in the test case while the human can navigate the whole system and several types of workflow, happy and sad paths, success, and failure of certain criteria quickly.

Automated systems are unable to generate original thought. They will perform only some specific tasks that are programmed. They also cannot generate effective feedback that a human user can provide. So, it’s suggested to perform Quality Control manually.

3.2.7. Low return on investment:

The main purpose of system tests is to save time and money. If test cases cannot provide these two then it’s useless. Some applications are simple and contain fewer modules. Testing these apps manually can be done by spending fewer resources on testing procedures.

For example, you are testing a simple form with a little bit of content and the business don’t care if it’s there or not. Another example could piece of application that is there but nobody uses it.

3.2.8. Installation and setup testing:

In installation and setup testing the system needs to test with different hardware and software such as loading CD-ROM, memory disks, and Tapes. Such types of systems also required manual testing.4

3.2.9. Test that requires to be run only for 1 time.

For Eg: For any application developed for a particular event, consider a “Festival Sale”. The Shopify store will develop a program for that particular sale to be valid for 1 month.

3.2.10  Other Factors

Some of the factors due to which test cases do not qualify for automation are:

• Incompatibility of automation tools with some of the application controls
• Dependency of the application on third-party services
• Unavailability of error-free test data for testing
• Lack of clarity in expected results
• Verification checks requiring manual intervention
• Interface with external application components not supported by the
• automation tool
• However in ideal scenarios 70-75% of manual test cases can be automated.

4.0 Our FRAMEWORK

We can help to identify test cases that are suitable for Automation. Once the test cases are identified, we can leverage our home-grown and proven test automation framework called RAFT to complete the automation in a very short period of time.

RAFT is a ready-to-use Test Automation framework that would help jump-start the Test Automation of Web, , API and Mobile Applications. Please click Request for the demo using the below link for the free demo

RAFT- ReUsable Automation Framework for Testing (novaturetech.com)

Author: admin   | Posted On: 9th March 2023   | Category: Article