3. Chapter 1
Quality Assurance!! What is that?
Chapter 2
Why do we really need to test our software?
Chapter 3
Microsoft Test Manager and “Friends”
Agenda
10. In March 2008, Waste Management, Inc., sued SAP for a complete failure of a $100 million software
installation. Waste Management stated that SAP could not run even the most basic processes.
In March 2004, the Ohio State Attorney General sued PeopleSoft for $510 million over a failed
installation of the PeopleSoft software at Cleveland University. It was stated, among other items,
that the software was “unstable” and that it had to install “hundreds of fixes.”
In January 2005, it was reported that the FBI’s Virtual Case File system built by Science Applications
International Corporation and which cost $170 million was being canceled. According to the
Washington Post, there were hundreds of problem reports, and many basic functions had not even
been tested at that time—and this was one month before delivery.
What if our software is not tested
as well as it should be ?
*Source from : Levinson, Jeff. Software Testing with Visual Studio 2010.
11. The Problems are
Your organization doesn’t test and you want to start testing.
Testing leads to finger pointing, which kills morale.
Projects are late because bugs are found late in the process.
Developers use one set of tools, and testers use another, and the
tools do not integrate.
The team is always finding and fixing bugs, but the customers
continue to find critical bugs.
12. Testers blame developers for not coding something right.
Developers blame testers for not using the software correctly.
13. “Customers always question
why there are so many bugs and why the developers and
testers aren’t working together better.”
