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

Test Automation Webinar Q&A Series – Software Testing and Test Automation Tools

Posted on: 20 May '09

Question: Slightly off topic question, from your experience, what tester to developer ratio do you recommend?

Response: You need enough testers to fully test (whatever that means in the context of the application or system under test) all code written by the developers on your team, including interoperability testing that will check interfaces to external systems, and any non-functional testing such as security, compliance, performance, accessibility, etc. For operating systems the ratio might be 1:1 or even 1.5:1 (testers to developers). I’ve seen IT and product teams with ratios of 1:12 and even 1:20, but they’re pulling in marketing and anyone else in the building during crunch time. I look for understaffing problems in anything lower than 1:5, but that’s just attitude, not something I’d bank on.

Question: As QA, what is the best way to prevent defect, whether or not it is design defect or actual code defect from happening?

Response: Set criteria for specific quality attributes and test for those criteria as early in the SDLC as possible, beginning with design. Review requirements and use cases (stories) and be sure the requirements are achievable and testable. In design, push development to write code that is easy (or easier) to test. Design hardened code. Profile functions for efficiency. Push for instrumentation. Drive developers as close to TDD as they can stand it. Insist on expert and peer review of developers’ code. Demand unit tests. Demand API automation. Demand using unit tests and API tests to achieve code coverage as close to 80% as you can get. Push for continuous integration, prefer workable code to meeting scheduled release dates.

Question: I am nervous about using Open source tools for automation. What are your thoughts of Open Source vs Vendor Tools we pay for (a la Mercury)?

Response: We’ve used Selenium for automation on many projects, building re-usable frameworks that enable reduction of cost as well as time to market. We’ve used other open source tools as well. You want open source tools that have lively community support. If you run across an open source tool whose developer community chatter has died off, that usually means that something better has come along and they’ve all gone there. The advantage of COTS tools is that their commercial interest requires that they respond to customer inputs, that they upgrade when new platforms or protocols render their last release obsolete, and that they provide or support the development of adapters, filters, and plug-ins. One disadvantage is that you’re dependent on the quality of their developers and their criteria for support. If you don’t have a platinum grade account, a vendor may not get to your query for months. Some tool vendors are much better than others at customer technical support. I’ve seen some great support from open source tools, people responding to queries on user forums within minutes of their posting, giving very practical workarounds or solutions. Then there’s the advantage of open source, that you can tweak your implementation at will. If you have the know-how, that’s a huge advantage.

Question: Any suggestion on which tool is the best know from your experience? I have only been into automation for few months.

Response: I couldn’t answer that without knowing what kind of testing you’re automating, the scale of your project, and what else you might want your test automation tool to do besides providing a scripting and execution environment.

The major tool vendors all have tools that work very well, and they all have features that appear to have received less attention during development than they should have. If you look at a review of test automation tools, or put one together yourself, you’ll find lots of positioning – this tool supports Linux but that one doesn’t, this one supports Windows 3.1 thru Windows Vista but this one only supports Win2K-Vista, this one handles distributed execution and remote operation while this one requires all machines to be on the same network, etc.

You’ll probably find out that the more careful you are in your shopping for tools, the more you’ll learn about your own requirements, and what opportunities are available through tooling that you didn’t know about.

  • Prem

    Good article, i really like it. I am doing a bit on research about Testing Automation and i found also macrotesting http://www.macrotesting.com to be very good source for testing tool and more.

    Thanks for your article

    cheers

    Prem

  • pooja

    What are the top 5 learning points in software testing that you think can be applied to a real life project in industry?

  • This post helps to show a new dimension of software testing services field. But I was curious to know that there’s lot of automation tool coming in cloud. What’s your suggestions on it?

  • Loved your post, keep adding more about it. would love to come back.