Introduction
In general, the Automation Test Life Cycle is common for any type of tool that you choose. Specifically, the automation process starts feasibility study followed by understanding the requirements clearly.
Once feasibility study completes the automation design starts on the agreed automation tool. During design, Automation Framework comes into picture, it helps to construct the code in well designed manner in such a way that if any new code injects with future functional change, then code should not mess up with the existing code. In this exercise automation tester has to under go so many dry run to ensue code is working as expected. Once code is ready, code will under go multiple reviews to ensure code has no breakages with Subject Matter Expert (SME) or Test Lead or Test Manager.
In future, based on any kind of application/functional change, automation code will under go maintenance and thereafter review will happens before deploying the code again.
Once feasibility study completes the automation design starts on the agreed automation tool. During design, Automation Framework comes into picture, it helps to construct the code in well designed manner in such a way that if any new code injects with future functional change, then code should not mess up with the existing code. In this exercise automation tester has to under go so many dry run to ensue code is working as expected. Once code is ready, code will under go multiple reviews to ensure code has no breakages with Subject Matter Expert (SME) or Test Lead or Test Manager.
In future, based on any kind of application/functional change, automation code will under go maintenance and thereafter review will happens before deploying the code again.
No comments:
Post a Comment