Automation Journey With Lean FT
One year ago, I have joined my new organization. I was pretty confident on my experience in automation. In long span of my testing carrier worked on many tools and technologies so never thought about any extra ordinary challenges in automation testing, reason behind was google. I always believe that google is always there to support us. As all myths has to be broken, same happened with this one also. Within one week of joining, I got a call from my manager, she said that trainings will be going on for a month but i want you to focus on framework and get fixed everything asap. It was a bit tensed situation for me, as I was not aware of company culture, their applications, tools and technology, here I feel every time google won’t help you, sometimes you need to fix these challenges by your past experiences.
When I started looking in to framework tool and technologies I was taken a back . It was total new experience for me. I worked on UFT, Selenium, Selenide Postman, JMeter, Soup UI kind of tools where tools provides lot of functionality which we leverage in our scripting.
But here UFT Developer/Lean FT tool was just medium to execute and parse the objects property apart from that everything was customized. Framework was half cooked and more complexed, I have analyzed that previous guy was techie and he wants to create dependency due to this he has written code in very much customized way. Being a technical guy, I have learnt the technique and I enjoyed his work but when it comes to leverage his work and producing ROI of the automation it is on of the nightmare for me.
Using these kinds of framework where teams are writing everything customized is waste of money and tool because tool is already providing you functionality. If you are creating those features in your framework by writing your own code, I believe it’s waste of time and money.
That’s why brainstorming and architecture design is very important where you analyze all the requirements and based on that you provide the solutions.
Every project is different most of the time you can replicate the previous design with some tweaks and twists but architect needs to review the requirement very carefully before providing the solutions. Sometimes a small changes in framework leads more time and cost.
Same happens with me framework was designed with lot of customization but no integration with apache poi’s and other third party apps like json, xml.
Writing integration code for these third party apps, framework needs lot of changes in code base so i will always recommended to managers and architects when ever solutions, please discuss with application owners also what are there requirements. Reviews at every layer is very important either automation team is identifying the technology stack or framework design or execution and report sharing….
I will share complete journey about tool selection to generate ROI in multiple parts which will help people to understand how to do solutioning…
To be continued …..