Featured Whitepapers
- Apples, Oranges, and Acorns - All Agile Development Tools Are Not the Same
- One's Enough for Agile Application Development Management
- Requirements Management 101 – 4 Basics Everyone Should Know
- Tips on Requirements Traceability – Learn How to Control Change and Improve Quality
- Scaling Continuous Integration to Large and Distributed Teams
Software Test Cases 101: The Basics
Posted by: Mike
in Subscriptions |
Comment (0)
Building test cases is about doing your best to find the worst in a program in order to deliver a quality product to thecustomer. Without a well-designed and executed test plan, the results can be catastrophic and very costly. For example,because of an error in the software, the first flight of the Ariane 5 rocket resulted in its complete destruction and the loss of four satellites at a cost of more than $370 million.
In the U.S. alone, software bugs cost the economy $59 billion2 back in 2002. Clearly, software defects must be found and corrected before unleashing new programs to the customer.
This article provides you with a basic understanding of software test cases. In addition, the article describes proven methods for building test cases that uncover the most defects with the minimum of time, effort and money.
Agile Marketplace - Announcements and Special Offers
The Business Case for ALM Transformation
Are legacy systems holding your company back? Breakthrough these technical constraints with an open and scalable environment that meets your unique business need to transform. There is no reason to be locked into an obsolete platform. The output of a number of recent transitions from legacy systems, this is practical white paper shares lessons learned and illustrates how guidance and enablement can pave the way for change.
Download this Whitepaper