Test Automation : Our Approach

From my experience, Manual testing leads to the tedious state when we have lot’s of repetitive testing and we may not able to think creative test scenarios as we have frequent releases and lots of workload in modern agile methodology.

So we need to implement the Test automation in such a way so it will reduce time and efforts of manual tester so he will focus on the creative thinking to test the product.

We need to maintain the balance between the Manual QA and Test Automation to get the best advantage of Test Automation but most of the Test Automation project is failed due to wrong implementation, stable and unorganized test scripts, slow test automation development. this will lead to project failure.

So when it comes to Automation, Have you ever think beyond just automating the test scenarios and just making the stable script. As ultimately Test Automation is only the approach to reduce the time and effort so that we can think about rare rare scenarios of the system due to which it might break. So we can overtake the issues before the release and achieve whole system coverage in testing.

I would like to share what I follow for Test Automation in JSbot.

I do give high priority to explore the entire system for a day, which will give idea about the product requirement, working functionality, targeted user, business requirement and other exploration which benefited me to design the test scenario from automation perspective, I’m focusing more on that so we can reduce the time and efforts.

I would share an incident, Once I got a very pleasing response from one of our US based client for my this kind of work flow, The project was firstly for Automation and we got the test cases ready from them just to automate, And for the demo purpose we deliver our test cases for their product. And guess what they literally found our test cases stronger and hand over us the Manual testing as well. Make sure you are being so precise while creating Test cases.

Once done with Manual Testing, we jump on our own testing framework called Selebot. It is built upon TestNG and Selenium and some utility methods that help to develop scripts faster. We’ve designed this in such a optimize way which will reduce your scripting time by 70%, So now it results in less overhead and efforts. Selebot actually gives a boost to the automation process and leads me towards to the best quality product and best advantage of it is flexible to any kind of requirement.

After automation, It’s time for the execute the test and reporting, which shows the overall summary where your product stands now. Which meant to be so specific that even nontechnical person can explain it with ease. We’ve our own reporting tool as well called VigoReport. It is integrated with Cucumber, TestNG, and Mocha. Which gives you more graphical representation about Test summary.

Go for Vigo now. I insist!

By using these tools, enable us to rapid script development, with reusable, scalable and stable scripts which maximize the ROI of our customer. In the conclusion, I am saying that Automation is a just approach to reduce the time, Make your testing verification so stronger which gives you an assurance that it won't get fail even in worst case scenario.

Think beyond the box! Test beyond the expectation!

Originally Published at Medium