<<PREVIOUS NEXT>>
Test automation has often been touted as an important part of an organization's quality strategy
However, it's not a silver bullet. In this article, We will discuss important considerations in determining when to invest in test automation, how to implement the program and how much of your application space should be automated.
We will address these questions in the context of the most common overall program factors. Using the information and considerations described, you’ll have the data to help you best determine how to implement test automation in your organization.
The questions of when, how, and how much are always dependent on the context of the overall program -- What is the test automation target? Key program factors include: the development paradigm, the quality objectives, and your deployment velocity. When, how and how much test automation to apply against a program is dependent on these factors -- the return on investment must align with these factors; otherwise, the long-term success of the test automation effort will be in jeopardy and almost certainly fail. The most common key program factors are:
Development paradigm (Agile, non-Agile, instrumented, non-instrumented)
Quality objectives (defect escape velocity)
Target deployment velocity (volume of new/enhanced functionality per release)
The focus of this article is on the implementation of a test automation program. It must be noted that test automation is not a silver bullet -- treating it as a “cure all” will certainly lead to disappointment. Test automation is an enabler, so if you have an effective (though overburdened) testing process then an appropriate test automation program will yield significant returns for your organization. Stay tuned for different approaches on test automation in next article....
When to Automate?
How to Automate?
How Much to Automate?
-Vikas Garg
A details talk on Test Automation best practices and methodologies.
Test automation has often been touted as an important part of an organization's quality strategy
However, it's not a silver bullet. In this article, We will discuss important considerations in determining when to invest in test automation, how to implement the program and how much of your application space should be automated.
Why Test Automation?
Test automation has always been an attractive alternative to expensive, time consuming and inconsistent manual testing. Test automation gives you quick test results, help manual test team to finish new builds testing quickly as regression test cases are tested through automation and it helps a lot during incremental build approach.When to invest in test automation?
How to implement or proceed with a test automation program?
How much of your manual testing effort should shift to test automation?We will address these questions in the context of the most common overall program factors. Using the information and considerations described, you’ll have the data to help you best determine how to implement test automation in your organization.
Key program factors
The questions of when, how, and how much are always dependent on the context of the overall program -- What is the test automation target? Key program factors include: the development paradigm, the quality objectives, and your deployment velocity. When, how and how much test automation to apply against a program is dependent on these factors -- the return on investment must align with these factors; otherwise, the long-term success of the test automation effort will be in jeopardy and almost certainly fail. The most common key program factors are:
Development paradigm (Agile, non-Agile, instrumented, non-instrumented)
Quality objectives (defect escape velocity)
Target deployment velocity (volume of new/enhanced functionality per release)
The focus of this article is on the implementation of a test automation program. It must be noted that test automation is not a silver bullet -- treating it as a “cure all” will certainly lead to disappointment. Test automation is an enabler, so if you have an effective (though overburdened) testing process then an appropriate test automation program will yield significant returns for your organization. Stay tuned for different approaches on test automation in next article....
When to Automate?
How to Automate?
How Much to Automate?
-Vikas Garg
No comments:
Post a Comment