Contact Us

Software Testing 3.0: Case Study #2

By | | Test Methods & Metrics

Introduction

Software Testing 3.0 is a strategic end-to-end framework for change based upon a strategy to drive testing activities, tool selection, and people development that finally delivers on the promise of software testing. For more details on the evolution of software testing and Software Testing 3.0 see:

Also see a previous case study on Software Testing 3.0 principals in action: Software Testing 3.0: Case Study #1

Following is a second case study of Software Testing 3.0 principals in action.

Testing Mature Software that was Never Tested

Environment Prior to LogiGear

A networking software company was testing core back-end functionality of their networking software manually utilizing a high-cost, on-shore based testing partner using manual testing methods. Because of the time consuming nature of manual testing, and the high cost of the on-shore manual testing partner:

  • The company was not testing the GUI component of their solution that they deemed to be “mature” and not subject to a lot of change.
  • The company’s customers were finding GUI bugs with every new release.
 

4,000 automated test cases

Coverage expanded from 0% to 90%

Automated GUI testing in only 20 machine hours

 

LogiGear implemented an automated testing program that made use of:

  • Low-cost off-shore LogiGear testing resources in Vietnam. These resources are all trained by LogiGear University in Software Testing 3.0 concepts and tools.
  • TestArchitectT, a tool set that integrates the latest methodologies and technologies in one easy-to-use package.

LogiGear has created an automated software testing program for this customer that:

  • Has implemented 4,000 automated software test cases for the GUI software
  • Expanded testing coverage from 0% to over 90% of the functionality of their application’s GUI
  • Runs the entire automated test suite in only 20 machine hours
  • Finds bugs that were previously found by the company’s customers helping to improve customer satisfaction with the software and lowering the burden on the vendor’s support staff
 

Generally accepted industry estimates indicate that bugs found by customers are at least 10 times more expensive than those found by software testing prior to release!

 

See: Quality Doesn’t Just Happen, By Judy McKay, CIO, May 24, 2007

Next Up

LogiGear’s testing resources are now moving on to automating testing for search and data import functionality. In the future, LogiGear will also be implementing an automated software testing program with low-cost Vietnam-based testing resources for the company’s back-end software replacing the existing expensive on-shore manual testing.

LogiGear Corporation

LogiGear Corporation LogiGear Corporation provides global solutions for software testing, and offers public and corporate software-testing training programs worldwide through LogiGear University. LogiGear is a leader in the integration of test automation, offshore resources and US project management for fast and cost-effective results. Since 1994, LogiGear has worked with hundreds of companies from the Fortune 500 to early-stage startups, creating unique solutions to exactly meet their needs. With facilities in the US and Vietnam, LogiGear helps companies double their test coverage and improve software quality while reducing testing time and cutting costs. For more information, contact Joe Hughes + 01 650.572.1400

TAG:

LogiGear Corporation
LogiGear Corporation provides global solutions for software testing, and offers public and corporate software testing training programs worldwide through LogiGear University. LogiGear is a leader in the integration of test automation, offshore resources and US project management for fast, cost-effective results. Since 1994, LogiGear has worked with Fortune 500 companies to early-stage start-ups in, creating unique solutions to meet their clients’ needs. With facilities in the US and Viet Nam, LogiGear helps companies double their test coverage and improve software quality while reducing testing time and cutting costs.

The Related Post

TestArchitect Corner: Capture Screens of Application Under Test during Automation Execution
Trying to understand why fails, errors, or warnings occur in your automated tests can be quite frustrating. TestArchitect relieves this pain.  Debugging blindly can be tedious work—especially when your test tool does most of its work through the user interface (UI). Moreover, bugs can sometimes be hard to replicate when single-stepping through a test procedure. ...
Key Success Factors for Keyword Driven Testing
Introduction Keyword-driven testing is a software testing technique that separates much of the programming work of test automation from the actual test design. This allows tests to be developed earlier and makes the tests easier to maintain. Some key concepts in keyword driven testing include:
Key Principles of Test Design
Test design is the single biggest contributor to success in software testing. Not only can good test design result in good coverage, it is also a major contributor to efficiency. The principle of test design should be “lean and mean.” The tests should be of a manageable size and at the same time complete and ...
August 2009 - Three Kinds of Measurement and Two Ways to Use Them
This article was originally featured in the July/August 2009 issue of Better Software magazine. Read the entire issue or become a subscriber. People often quote Lord Kelvin: “I often say that when you can measure what you are speaking about, and express it in numbers, you know something about it; but when you cannot express ...
Test Everything All the Time...
Back from more training, I was up at a client in Bellevue and really enjoyed teaching a performance class to a world class testing organization. I found that the students were very receptive to many of the concepts and ideas that the class offers.
Testing Under Pressure: Relieving the "Crunch Zone"
Introduction This article discusses the all-too-common occurrence of the time needed to perform Software Testing being short changed as specification, development, and unforeseen “issues” cause the phases prior to testing to expand. The result is that extreme pressure is placed upon the testing organization to perform the testing function within a reduced time frame. The ...
How to Measure Testing Success
Introduction All too often, senior management judges Software Testing success through the lens of potential cost savings. Test Automation and outsourcing are looked at as simple methods to reduce the costs of Software Testing; but, the sad truth is that simply automating or offshoring for the sake of automating or offshoring will only yield poor ...
LogiGear Magazine - May 2011 - the Test Process Improvement Issue
LogiGear Magazine – May 2011 – The Test Process Improvement Issue
Something Old, Something New: Requirements and Specifications
Differences in interpretation of requirements and specifications by programmers and testers is a common source of bugs. For many, perhaps most, development teams the terms requirement and specification are used interchangeably with no detrimental effect. In everyday development conversations the terms are used synonymously, one is as likely to mean the “spec” as the “requirements.”
Rob Lambert: The Social Tester
Creative Director at the Software Testing Club, Rob Lambert always has something to say about testing. Lambert regularly blogs at TheSocialTester where he engages his readers with test cases, perspectives and trends. “Because It’s Always Been Done This Way” Study the following (badly drawn) image and see if there is anything obvious popping in to ...
Why You Need a Software Specific Test Plan
Experience-based recommendations to test the brains that drive the devices In essentially every embedded system there is some sort of product testing. Typically there is a list of product-level requirements (what the product does), and a set of tests designed to make sure the product works correctly. For many products there is also a set ...
Computer Scientist - D. Richard Kuhn Will Provide Some Insights on How to Become a Software Tester a...
D. Richard Kuhn – Computer Scientist, National Institute of Standards & Technology LogiGear: How did you get into software testing? What did you find interesting about it? Mr. Kuhn: About 10 years ago Dolores Wallace and I were investigating the causes of software failures in medical devices, using 15 years of data from the FDA. ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe
SHARE: Facebooktwitterlinkedinmail