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

Boeing Software Scandal Highlights Need for Full Lifecycle Testing
It’s a bird! It’s a plane! It’s a software defect of epic proportions.
How to Reduce Duplicate Bug Reporting by 75%
Reducing the pester of duplications in bug reporting. Both software Developers and Testers need to be able to clearly identify any ‘Bug’, via the ‘Title’ used for the ‘Bug Report’.
Mindmaps: a Killer Way to Increase Your Test Coverage
Plan your Test Cases with these Seven Simple Steps What is a mind map? A mind map is a diagram used to visually organize information. It can be called a visual thinking tool. A mind map allows complex information to be presented in a simplified visual format. A mind map is created around a single ...
LogiGear Magazine March Testing Essentials Issue 2017
LogiGear Magazine March Testing Essentials Issue 2017
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.
Key Principles of Test Design
Regardless of the method you choose, simply spending some time thinking about good test design before writing the first test case will have a very high payback down the line, both in the quality and the efficiency of the tests. Test design is the single biggest contributor to success in software testing and its also ...
Blogger of the Month: 3 Simple Reasons Why Your Bug Report Sucks
First, let me ask you a few questions. Are your bugs often rejected? Are your bugs often assigned back to you and discussed back and forth to clarify information? Do your leaders or managers often complain about your bugs?
VISTACON 2010 Keynote - the Future of Testing by BJ Rollison
VISTACON 2010 – Keynote: The future of testing THE FUTURE OF TESTING BJ Rollison – Test Architect at Microsoft VISTACON 2010 – Keynote   BJ Rollison, Software Test Architect for Microsoft. Mr. Rollison started working for Microsoft in 1994, becoming one of the leading experts of test architecture and execution at Microsoft. He also teaches ...
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 ...
July 2009 - Issues About Metrics About Bugs
This article was originally featured in the May/June 2009 issue of Better Software magazine. Read the entire issue or become a subscriber. In my travels, I’ve worked with a number of companies that have attempted to assess the quality of their testing — or worse, their testers — using poorly considered metrics. Sometimes the measurement ...
LogiGear Magazine March Issue 2018: Under Construction: Test Methods & Strategy
LogiGear Magazine March Issue 2018: Under Construction: Test Methods & Strategy
Who Cares About Test Plans? You Should!
Test plans have a bad reputation, and perhaps, they deserve it! There’s no beating around the bush. But times have changed. Systems are no longer “black boxes” where QA Teams are separated from design, input, and architecture. Test teams are much more technically savvy and knowledgeable about their systems, beyond domain knowledge. This was an old ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe
SHARE: Facebooktwitterlinkedinmail