| | |  | Software Engineering | Home » » » Manage Software Testing | | | | | | | Product Promotions: | | | | | Description: | | Whether you are inheriting a test team or starting one up, Manage Software Testing is a must-have resource that covers all aspects of test management. It guides you through the business and organizational issues that you are confronted with on a daily basis, explaining what you need to focus on strategically, tactically, and operationally. Using a risk-based approach, the author addresses a range of questions about software product development. The book covers unit, system, and non-functional tests and includes examples on how to estimate the number of bugs expected to be found, the time required for testing, and the date when a release is ready. It weighs the cost of finding bugs against the risks of missing release dates or letting bugs appear in the final released product. It is imperative to determine if bugs do exist and then be able to metric how quickly they can be identified, the cost they incur, and how many remain in the product when it is released. With this book, test managers can effectively and accurately establish these parameters. | | | Product Details: | | | Author:
| Peter Farrell-Vinay | | Hardcover:
| 600 pages | | Publisher:
| Auerbach Publications | | Publication Date:
| March 07, 2008 | | Language:
| English | | ISBN:
| 0849393833 | | Product Width:
| 181.0 centimeters | | Product Height:
| 253.5 centimeters | | Product Weight:
| 2.68 pounds | | Package Length:
| 9.9 inches | | Package Width:
| 7.2 inches | | Package Height:
| 1.5 inches | | Package Weight:
| 2.55 pounds | | Average Customer Rating:
|  based on 1 reviews |
| | | | Customer Reviews: | |
Average Customer Review:
 ( 1 customer reviews )
Write an online review and share your thoughts with other customers.
Most Helpful Customer Reviews
4 of 4 found the following review helpful:
Mixed viewsNov 22, 2009
By Viswanathan Rajeswaran
"V. Rajeswaran"
I have read many testing books and this book surely has lots of material which is not covered elsewhere. However, the book frustrates you when you try out the examples or try to figure out what to do and what to leave out (theoretical). Those trying to learn things not offered in regular books can find this insightful.
Be warned that many ideas are not practically implementable - for example 18.10.6 - Bug seeding model where we deliberately insert bugs in code to estimate the # of defects. This is NEVER done in real life (my experience) since we have difficult time doing the actual project and eliminating the real bugs. The author does not warn you of this. There are many other cases where the author should warn you if its theoretical or practical some examples -
(1) Section 18.2.1 (Revised) Propagation Analysis Algorithm - Not possible in real software development with deadlines.
(2) 18.2.5 Revised Execution Analysis Algorithm
The author should have given the data and XLS in his blog (very difficult to locate) so that the readers can use the information. I vainly tried the example in 18.3.1 How to Calculate Influences on Performance and was so frustrated that he changed the columns between figure 18.2 and 18.3 and gives so much data in 6th decimal (making it useless for the readers when we are not able to follow).
On the positive side - there are a lot of insight in terms of reliability covered here. The references are very good and useful. It should have more stars if the XLS were provided or examples made more understandable.
| | |
|
