Software Testing 3.0: Case Study #1

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:

  1. The Early Evolution of Software Testing
  2. Software Testing 3.0: Delivering on the Promise of Software Testing

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

MX Logic Inc.:
Automation Expands Testing Coverage, Reduces Testing Time

Environment Prior to LogiGear

MX Logic is a leading provider of email and web managed security services. The company was running a suite of 423 software tests manually to test their security software. Manual Testing was so time consuming that:

  • Manual Testing of their software’s functionality was taking approximately 240 person-hours to run
  • Build acceptance testing was done on an ad-hoc, time-permitting basis

LogiGear’s Solution

LogiGear implemented an Automated Testing program for MX Logic 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.
  • TestArchitect, a tool set that integrates the latest methodologies and technologies in one easy-to-use package.

The Automated Software Testing solution implemented by LogiGear allowed the company:

    • To automate existing tests and expanded test coverage to 945 automated test cases that run in 150 to 160 machine hours (the same tests run manually would consume 480 to 500 man hours).
    • To expand testing coverage from 50% to 90%
    • To use a subset of these tests to implement regular automated build acceptance testing that runs in 2 machine hours (the same would take 1 person day manually)
LogiGear has delivered an innovative turnkey solution that is fully automated, low cost and has expanded our testing coverage by 90%.

While reviewing any Test Automation initiative it is important to understand that a successful Automation project requires care and maintenance. Not only does LogiGear provide MX Logic with an excellent Automation tool in TestArchitect, it provides me with the cost effective resources to enhance and maintain our Automation projects. With a comparable feature set to more expensive licensed tools, my Automation budget can be utilized on both the tool and the engineers to support it for the same price. And this guarantees the success of our Automation, where others fail!

– Jamie Tischart, Director,
Quality Assurance, MX Logic

Coverage expanded from 50% to 90%

Automated test coverage expanded from 10% to 80%

Twice as many tests tested in less time (150 machine hours vs. 240 person hours)

Added regular build-acceptance testing

Added production portal performance testing

    • To reuse the automated test suite release after release with only the addition of a small number incremental test cases to test new functionality
  • To avoid staff growth in their domestic operations
Using the difference in cost between fully-burdened U.S. based resources and Vietnam based resources, LogiGear estimates that this level of Automated Testing effort done manually would have cost the company an additional $1 million or more. LogiGear’s Automated Software Testing efforts have expanded testing coverage and effectiveness while avoiding significant additional expense.
LogiGear’s Automated Software Testing efforts expanded testing coverage and effectiveness while avoiding significant additional expense.

In addition, LogiGear created performance testing to help MX Logic monitor their customer experience on their production portal. They run this daily to ensure that their customer experience is not negatively affected by any new features or Internet traffic spikes.

Next Up

LogiGear will be producing an additional 300 automated test cases to cover new functionality that MX Logic will be adding to their software. This will bring the total number of test cases to nearly four times the company’s original manual test suite.

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

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

Karen N. Johnson began as a technical writer in 1985 and later switched to software testing in 1992. She maintains a blog at TestingReflections, a collaborative site where she is featured as a main contributor. In her latest entry, she discusses search testing with different languages. Here is an excerpt from her blog: “I started ...
When it is out of the question to delay delivery, the solution is a prioritization strategy in order to do the best possible job within the time constraints. The scenario is as follows: You are the test manager. You made a plan and a budget for testing. Your plans were, as far as you know, ...
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 ...
One of the most dreaded kinds of bugs are the ones caused by fixes of other bugs or by code changes due to feature requests. I like to call these the ‘bonus bugs,’ since they come on top on the bug load you already have to deal with. Bonus bugs are the major rationale for ...
The Testing Domain Workbook is the most extensive and exhaustive work you will ever find on a specific testing technique (or related techniques if you include equivalence class analysis and boundary testing as the book does). What I like best is the combination of academic background and roots combined with practical experience and industrial practice. All the concepts are ...
Training has to be fun. Simple as that. To inspire changed behaviors and adoption of new practices, training has to be interesting, motivating, stimulating and challenging. Training also has to be engaging enough to maintain interest, as trainers today are forced to compete with handheld mobile devices, interruptions from texting, email distractions, and people who think they ...
LogiGear Magazine March Testing Essentials Issue 2017
PWAs have the ability to transform the way people experience the web. There are a few things we can agree we have seen happen. The first being that we figured out the digital market from an application type perspective. Secondly, we have seen the rise of mobile, and lastly, the incredible transformation of web to ...
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 ...
Most have probably heard the expression ‘less is more‘, or know of the ‘keep it simple and stupid‘ principle. These are general and well-accepted principles for design and architecture in general, and something that any software architect should aspire to. Similarly, Richard P. Gabriel (a major figure in the world of Lisp programming language, accomplished poet, and currently ...
LogiGear Magazine – May 2011 – The Test Process Improvement Issue
Companies generally consider the software they own, whether it is created in-house or acquired, as an asset (something that could appear on the balance sheet). The production of software impacts the profit and loss accounts for the year it is produced: The resources used to produce the software result in costs, and methods, tools, or ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe