Automation Framework is a big buzz word in IT today, especially in the QA world and everyone wants to get on the bandwagon. There are many sources through which automation can be learned however, automation framework is an elusive concept for most people. There are resources who are experts in coding, finding it difficult to design an automation framework alone since they have limited knowledge on how to design a framework or not enough research has been done to understand how to design a framework. There are some common mistakes that automation framework designers do which makes the framework difficult to use and maintain.
Over the years, I have discovered that the art of designing an automation framework is not about getting help from others or getting some training, but its’ the past mistakes that I made which taught me how to avoid them. To make automation a success it is very important to have a good robust automation framework in place which will act as the core foundation for the automation life cycle. If the framework does not support all the requirements or is not constructed correctly then it might impact the automation ROI, maintenance and become very expensive. In order to create an effective automation framework, you should avoid rushing in and begin to write code. However, you should spend sufficient time to collect the requirements from every aspect.
Below are few points to keep in mind when designing an automation framework: