Transition from Manual to Automated Testing – Key Considerations

Course Level




Total Chapters



Course content

5 Chapters30m
This chapter looks at test automation’s investment cost, compared to traditional approaches. It also introduces essential elements involved in the transition, including factors to consider when implementing automated regression and new feature testing.
Considerations for Essential Types of Automated Testing

Chapter 5 - Course Summary

This course discusses the basics and best practices to help your team ensure a smooth transition from manual to automated testing. The course’s materials are essential to know before choosing any tools or frameworks to apply test automation.

In four chapters, you will learn about the:

  • Types of automated testing to prioritize and key considerations when implementing them
  • Common approaches and techniques to create automated tests
  • Comparison between open-sourced and commercial test automation tools and how to choose one for your team
  • Test reporting and metrics to measure the quality and impact of test automation solutions

Chapter 1 - Considerations for Essential Types of Automated Testing

Considerations for Essential Types of Automated Testing


Effective testing is key to a successful project. Yet managing and running tests manually take time and money so that automated testing came into play with the objective of maximizing efficiency and delivering a high-quality product in a cost-effective manner. However, the process of switching from manual to automated testing is obviously NOT that simple.


In this chapter, we'll show you how that process works and which elements are involved, including factors to consider when implementing automated regression testing, implementing automation of Confirmation Testing as well as implementing automation within New Feature Testing.


Just for more information, although at first development teams may think that the cost of investing in test automation is somewhat higher than the traditional technique, in the long run, aggregately the cost will turn out to be much lower. Looking at the graph, you can see the orange line, which represents the cost in manual testing cases will continue going up in positive correlation with the time expansion.


Now, let's move to the first consideration that is implementing automated tests for regression testing. Regression testing provides a great opportunity to use automation, as it refers to the type of testing that ensures developed and tested software still appropriately performs without any unexpected side effects after modifications.


In developing steps to prepare to automate regression tests, a number of questions must be asked: how frequently should the tests be run, do tests share data, and what pre-conditions are required before test execution. Each of these questions is explained more in detail in the following sections.


Tests that are executed often as part of regression testing are the best candidates for automation. Automation, like manual testing, requires a certain amount of effort to conduct so that only higher-frequency tests are preferentially automated. Meanwhile, the remaining low-frequency regression tests can still be tested manually.


Tests often share data. This activity can occur when tests use the same record of data to execute the different applications under the test's functionality. An example of this might be test case ''A'' which verifies an employee's available time for vacation while test case ''B'' refers to courses taken as part of these employees' career development goals. Each test case uses the same employee information but verifies different aspects.


In a manual test environment, the employee data would typically be duplicated many times across each test case. However, for automated tests, shared data should be feasibly stored and accessed from a single source to avoid the introduction of errors.


Next, how about we'll walk you through the test preconditions part? Most of the time, a test cannot be executed properly without the setting initial conditions stage. These conditions may include selecting the correct database, the test data set, or even starting up initial values or parameters. Many of these initialization steps that are required to establish a test's precondition can all be automated, allowing for a more reliable and independent solution. As regression tests are converted to automation, these preconditions also need to be a part of the automation process.


Moving forward to the next segment, we'll go deep into which factors to consider when implementing automation of confirmation testing. Confirmation testing particularly is performed to follow a code fix that addresses a reported defect.


A tester typically follows necessary steps in confirmation testing to ensure that the defect no longer exists and prevent its reproduction later. Defects have a way of reintroducing themselves into subsequent releases, therefore automation is in need in this case to reduce repetitive execution time for confirmation testing. Keep in mind that tracking automated confirmation tests allows for additional reports of how many times and cycles expended in resolving defects.


Automated confirmation tests can be incorporated into a standard automated regression suite, or subsumed into existing automated tests. With either approach, the value of automating defect confirmation testing still holds. Along with confirmation testing, regression testing is necessary to ensure new defects have not been introduced as a side effect of the defect fix. Impact analysis may be required to determine the appropriate scope of regression testing.


In general, it is easier to automate test cases for new functionality rather than the existing ones. Test engineers, based on their knowledge can explain to developers and architects which factors are exactly needed to consider when implementing automation within new feature testing. Don't worry, we cover this topic for you right away.


As new features are introduced into an application under test, testers are required to develop new tests against these new features and corresponding requirements. The current test automation solution should be evaluated to confirm that it still meets the needs of new features. This investigation includes, but does not limit to, the existing approach and test tools used, as well as third-party development tools.


Changes to the test automation solution, if any, must also be evaluated so it does not affect the performance of existing solutions. If a new feature is implemented with, as an example, a different class of object, testware components may need to make additions. Besides, compatibility with existing test tools must be evaluated or, where necessary, alternative solutions identified. For example, if using a keyword-driven approach, it is necessary to develop new or modify the existing keywords to accommodate the new functionality. Last but not least, one needs to determine if the existing test automation solution will continue to meet current framework standards. Testers now may have to ask themselves: are implementation techniques still valid, or is a new architecture required, and can this be done by extending current capability.


In summary, this chapter introduces the process of switching from manual testing to automated testing environments. Specifically, it lists out in detail the factors to consider when implementing automated regression testing, Confirmation Testing and New Feature Testing.

Chapter 2 - Approaches and Methods to Automate Test Cases

Chapter 3 - Automation Tool Evaluation and Selection

Chapter 4 - Test Automation Reporting and Metrics

Chapter 5 - Course Summary


Materials include

  • 30 minute on-demand course

  • Lifetime access

  • Certificate of completion

    Coming soon