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
Understanding Software Test Cases
Building test cases is about doing your best to find the worst in a program in order to deliver a quality product to the customer. 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 eBook provides you with a basic understanding of software test cases. In addition, the eBook describes proven methods for building test cases that uncover the most defects with the minimum of time, effort and money.
http://www.elementool.com/ebook/SoftwareTestCases.pdf
Agile - Changing role of QA

Most agree the role of a tester will change within agile. Ask a group of so-called experts exactly what these changes are and you'll probably get a different answer from each of them!
Testing Scrum Core Practices
Being apprehensive prior to joining my first agile scrum team, I spent many hours surfing the web for some kind of process model (mainly so I knew what I was letting myself into).
Because of the nature of agile/scrum and the fact there are so many different flavours to it, this was more difficult than first thought. However, with my experience and a little help from the web, I have managed to put together a list of core practices that make up the scrum process.
Agile Testing Myths - Q & A
"Agile is an excellent opportunity for QA to take leadership of the processes. Rather than take a back seat while developers drive the ship, testers can now take the lead".
"Who else is better placed to bridge the gap to understand … what is required, how it can be achieved and how it can be assured prior to deployment? This requires tester to be be fluent in agile themselves".
With bold statements like these, I receive quite a few emails from testers with concerns about switching to agile. Continue to see TesterTroubles Q & A.
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

