This is a common question I hear from many testing professionals and customers. The question further becomes complex with the introduction of open source in it given the complexity in identifying a test automation tool that is best for the project.
I am listing down a few best practices in identifying a right open source test automation tool / framework for your project:
– Identify categorically the nature of application under test say, thin client / thick client / web Services.
– Prepare a checklist of features that the open source tool should support, ensure that the automation objectives met or not.
– Identify the open source / freeware tools that best suits your automation objective, say Selenium-Grid / TestNG for creating concurrent test script execution.
– Perform a functional automation tool evaluation (for details refer tables below), this mechanism for test automation projects is to correlate, identify the best fit single / multiple combinations of open source tools that maps your automation objectives.
Tool evaluation provides a comprehensive overall-weighted score, with which we can clearly identify the best possible combination and as a best practice we ensure to architect the framework with a combination of open source tools.
In my next blog I will provide an exhaustive list of criteria that will help you better evaluate the tool and align it with your need.