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
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.
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, ...
They’ve done it again. Gojko Adzic, David Evans and, in this book, Tom Roden, have written another ‘50 Quick Ideas’ book. And this one is equally as good as the previous book on user stories. If not even better.
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 ...
“Combinatorial testing can detect hard-to-find software faults more efficiently than manual test case selection methods.” Developers of large data-intensive software often notice an interesting—though not surprising—phenomenon: When usage of an application jumps dramatically, components that have operated for months without trouble suddenly develop previously undetected errors. For example, newly added customers may have account records ...
March Issue 2019: Leading the Charge with Better Test Methods
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 ...
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 ...
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 ...
Are you looking for the best books on software testing methods? Here are 4 books that should be on your reading list! The Way of the Web Tester: A Beginner’s Guide to Automating Tests By Jonathan Rasmusson Whether you’re a traditional software tester, a developer, or a team lead, this is the book for you! It ...
MARCH 2016_ TEST DESIGN ISSUE
LogiGear Magazine – July 2011 – The Test Methods & Strategies Issue
As I write this article I am sitting at a table at StarEast, one of the major testing conferences. As you can expect from a testing conference, a lot of talk and discussion is about bugs and how to find them. What I have noticed in some of these discussions, however, is a lack of ...