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
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 ...
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 March Testing Essentials Issue 2017
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. ...
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. ...
Let’s look at a few distinctions between the two process improvement practices that make all the difference in their usefulness for making projects and job situations better! An extreme way to look at the goals of these practices is: what makes your work easier (retrospective) versus what did someone else decide is best practice (post-mortem)? ...
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: Software Testing 3.0: Delivering on the Promise of ...
Please note: This article was adapted from a blog posting in Karen N. Johnson’s blog on July 24, 2007. Introduction The password field is one data entry field that needs special attention when testing an application. The password field can be important (since accessing someone’s account can start a security leak), testers should spend more ...
Test organizations continue to undergo rapid transformation as demands grow for testing efficiencies. Functional test automation is often seen as a way to increase the overall efficiency of functional and system tests. How can a test organization stage itself for functional test automation before an investment in test automation has even been made? Further, how ...
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 ...
Has this ever happened to you: You’ve been testing for a while, perhaps building off of a branch, only to find out that, after all of this time, there is something big wrong. It’s a bad build and now you have to go backwards, fix something, and get a new build. Basically, you just wasted ...
I’ve been reviewing a lot of test plans recently. As I review them, I’ve compiled this list of things I look for in a well written test plan document. Here’s a brain dump of things I check for, in no particular order, of course, and it is by no means a complete list. That said, if you ...