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:
- The Early Evolution of Software Testing
- 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 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.
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 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
The 12 Do’s and Don’ts of Test Automation When I started my career as a Software Tester a decade ago, Test Automation was viewed with some skepticism.
Explore It! is one of the very best software testing books ever written. It is packed with great ideas and Elisabeth Hendrickson’s writing style makes it very enjoyable to read. Hendrickson has a well-deserved reputation in the global software testing community as someone who has the enviable ability to clearly communicate highly-practical, well-thought-out ideas. ...
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 ...
With complex software systems, you can never test all of the functionality in all of the conditions that your customers will see. Start with this as a fact: You will never test enough! Step 2 in getting started is to read and re-read The Art of Software Testing by Glenford Myers. This classic will set the ...
The key factors for success when executing your vision. There is an often cited quote: “…unless an organization sees that its task is to lead change, that organization—whether a business, a university, or a hospital—will not survive. In a period of rapid structural change the only organizations that survive are the ‘change leaders.’” —Peter ...
When You’re Out to Fix Bottlenecks, Be Sure You’re Able to Distinguish Them From System Failures and Slow Spots Bottlenecks are likely to be lurking in your application. Here’s how you as a performance tester can find them. This article first appeared in Software Test & Performance, May 2005. So you found an odd pattern ...
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 ...
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.”
It’s a bird! It’s a plane! It’s a software defect of epic proportions.
From cross-device testing, to regression testing, to load testing, to data-driven testing, check out the types of testing that are suitable for Test Automation. Scene: Interior QA Department. Engineering is preparing for a final product launch with a deadline that is 12 weeks away. In 6 weeks, there will be a 1 week quality gate, ...
There are many ways to approach test design. These approaches range from checklists to very precise algorithms in which test conditions are combined to achieve the most efficiency in testing. There are situations, such as in testing mobile applications, complex systems and cyber security, where tests need to be creative, cover a lot of functionality, ...