Phy-gital Roundtable: Breakfast Roundup from Germany and Netherlands

02 May '15 | Debjyoti Paul

German Shoppers: Meet Them in the Fast Lane to Phy-gital

15 January '15 | Ralf Reich

Shoppers Will Share Personal Information (But They Don’t Want to be “Friends”)

15 January '15 | Anil Venkat

Modernize or Perish: Property and Casualty Insurers and IT Solutions

14 January '15 | Manesh Rajendran

Benelux Reaches the Phy-gital Tipping Point: Omnichannel Readiness is Crucial

13 January '15 | Anil Gandharve

The New Omnichannel Dynamic: Finding Core Principles Across Industries

13 January '15 | Debjyoti Paul

Technology does not disrupt business – CIO day 2014 Roundup

02 December '14 | Anshuman Singh

Apple Pay – The Best Is Yet To Come

02 December '14 | Indy Sawhney

Digital transformation is a business transformation enabled by technology

01 December '14 | Amit Varma

3 Stages of FATCA Testing and Quality Assurance

06 October '14 | Raman Suprajarama

3 Reasons why Apple Pay could dominate the payments space

18 September '14 | Gaurav Johri

Beacon of Hope: Serving Growth and Customer Satisfaction

05 August '14 | Debjyoti Paul

The Dos and Don’ts of Emerging Technologies Like iBeacon

30 July '14 | Debjyoti Paul

What You Sold Us On – eCommerce Award Finalist Selections

17 July '14 | Anshuman Singh

3 Steps to Getting Started with Microsoft Azure Cloud Services

04 June '14 | Koushik Ramani

8 Steps to Building a Successful Self Service Portal

03 June '14 | Giridhar LV

Innovation outsourced – a myth or a mirage or a truth staring at us?

13 January '14 | Ramesh Hosahalli

What does a mobile user want?

03 January '14 | Gopikrishna Aravindan

How should I identify the best open source test automation tools / frameworks for my project?

Posted on: 20 July '10

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.