cdc-coteauxdegaronne
» » Effective Methods for Software Testing
eBook Effective Methods for Software Testing ePub

eBook Effective Methods for Software Testing ePub

by William E. Perry

  • ISBN: 0471060976
  • Category: Programming
  • Subcategory: Computers
  • Author: William E. Perry
  • Language: English
  • Publisher: *A Wiley-QED Publication; 1 edition (October 13, 1995)
  • Pages: 560
  • ePub book: 1618 kb
  • Fb2 book: 1977 kb
  • Other: azw mobi lrf lrf
  • Rating: 4.3
  • Votes: 493

Description

For several years, I have recommended Bill Perry's Effective Methods for Software Testing, 2nd Ed to people who are looking for testing processes they can customize and apply quickly. I have also included this book as a reference text in many of my testing courses.

For several years, I have recommended Bill Perry's Effective Methods for Software Testing, 2nd Ed to people who are looking for testing processes they can customize and apply quickly. Obviously, I feel that the book is very helpful to software testers.

Effective Methods for Software Testing. The core of this book is the step-by-step process for testing software. Published simultaneously in Canada. ISBN-13: 978-0-7645-9837-1 ISBN-10: 0-7645-9837-6. Manufactured in the United States of America. 10 9 8 7 6 5 4 3 2 1. 3MA/qv/qu/qw/in.

Surviving the Top Ten Challenges of Software Testing: A People-Oriented Approach by. William E. Perry, Randall W. Rice.

Written by the founder and executive director of the Quality Assurance Institute, which sponsors the most widely accepted certification program for software testing Software testing is a weak spot for most developers, and many have no system in place to find and correct defects quickly and efficiently This comprehensive resource provides step-by-step guidelines, checklists, and templates for each testing activity, as.

This book provides the latest in standards for measuring how good your organisation's commitment to software testing is and many ways to improve it. In all, with its numerous lists and practical step-by-step guide to testing, this book points the way toward more economical and effective software testing.

Автор: Perry, William E. Название: Effective methods for software testing Издательство: Wiley Классификация .

This book covers the regulatory developments affecting software testing, including Sarbanes-Oxley Section 404, and provides guidelines for agile testing and testing for security, internal controls, and data warehouses.

We’re dedicated to reader privacy so we never track you. We never accept ads. But we still need to pay for servers and staff.

We’re dedicated to reader privacy so we never track you. I know we could charge money, but then we couldn’t achieve our mission: a free online library for everyone. This is our day. Today.

a great book for the software organization trying to improve. com User, March 11, 2004.

Marc Roper, Software Testing, McGraw-Hill Book C. London, 1994. 5. Gordon Schulmeyer, Zero Defect Software, McGraw-Hill, New York, 1990. 6. Watts Humphrey, Managing the Software Process, Addison Wesley Pub. Co. In. Massachusetts, 1989. 7. Boris Beizer, Software System Testing and Quality Assurance, Van Nostrand Reinhold, New York, 1984. 8. Glenford Myers, The Art of Software Testing, John Wiley & Sons In. New York, 1979.

Software Engineering/Software Testing

All the proven testing strategies, tools, and techniques you need to guarantee that your applications do exactly what they're supposed to do!

When it comes to software performance, your customers hate surprises. And the best way to ensure that your systems don't give them any is by implementing a rigorous, fully integrated testing regime that encompasses every phase of the software development life cycle—from design to installation, and beyond. Now, in Effective Methods for Software Testing, internationally recognized software testing expert William Perry provides you with everything you need to do just that, including:

Tests for all types of software systems, including Client/Server and LANs Clear, step-by-step guidelines on how to establish a test approach and overall testing plan Proven methodologies for conducting tests quickly and efficiently 15 testing techniques covering all phases of the development life cycle 42 testing tools and 30 metrics Detailed instructions on how to seamlessly integrate the tools and techniques into the development life cycle Techniques for evaluating test effectiveness Dozens of worksheets and checklists for use during every step of the testing process

Short on theory and long on nuts-and-bolts information and guidance, Effective Methods for Software Testing arms you with what you need to guarantee that your customers get what they deserve—the most usable, bug-free software possible.

Comments

Aver Aver
For several years, I have recommended Bill Perry's Effective Methods for Software Testing, 2nd Ed to people who are looking for testing processes they can customize and apply quickly. I have also included this book as a reference text in many of my testing courses. Obviously, I feel that the book is very helpful to software testers.

In the third edition, there are two fewer chapters, but the coverage of topics has been revised to include areas such as agile testing, the role of testing in software development methodologies, testing internal controls, and an expanded discussion on security testing.

The eleven-step testing process in the second edition has been streamlined to seven steps in this edition. In this process, you will find everything you need to design and customize your own testing process all the way from test planning, through the various phases of testing (static testing, unit testing, integration testing, system testing and acceptance testing), and even through post-implementation testing. The process also addresses analyzing and reporting test results, which also discusses test metrics.

The reasons I'm such a fan of the book are: 1) You get complete templates and examples, including checklists (although the CD contains PDF versions of the forms which would still need to be re-created in a word processor to be usable in electronic format). 2) The book is process-oriented as opposed to a collection of techniques. Collections are fine, but you still need a way to apply them. That's where the processes come in helpful. Also, the workbench process framework is helpful in defining your own processes. 3) These are practical and proven processes that have been used in a variety of organizations worldwide. There is very little theory and a lot of practical application as shown by the examples. 4) You don't have to be a highly mature organization to start applying these techniques. Whether you are CMMi Level 1 or 5, you can still find this information useful. 5)The book also addresses specific topics such as testing commercial-off-the-shelf software and data warehouse applications.

This is a thick book, but then again, it is not designed to be read from front to back. I use it as a desk reference and a collection of processes to help get the job of testing done. I can save hours of work in designing processes by checking here first. My attitude is to tailor the processes to meet my needs. It's also my first stop when doing research. Personally, I like processes because I can transfer them to others and have something tangible to study and improve. However, I will say that if you are "process averse" you will probably not find this book as helpful as someone who does process-based work. The processes described in the book are not heavy ones, though.

This is a good resource for software testers written by someone who has been writing and working in this profession for many years.

Readability - 4

Coverage of topics - 5

Depth of coverage - 5

Credibility - 5

Accuracy - 5

Relevance to software quality - 5

Overall - 5

Reviewed by Randy Rice
Nto Nto
Timely, very good quality, and great price.
Vizuru Vizuru
There are a few things to say in favour of this book:
1. It does walk through on how to approach testing in your organization (however, it is definitely oriented towards organizations with established testing principles).
2. It does give you some background information on software testing. Sadly, these are mainly explained in a textbook like manner, making them hard to digest.
3. It provides a thorough, detailed and tested methodology for software testing throughout the various life cycles. Yet again, due to the book's textbook like manners, I found it hard to actually implement the offered methodologies.
Whatever positive attributes the book has to offer, they pale in comparison to the book's negative aspects:
1. Total unreadability: The book written in such a boring manner, you will find yourself reading every page thrice, and still lack the satisfaction of being able to quote the meaning of what you just read.
2. Lack structure: Paragraphs are thrown in one after the other; it's hard to decipher what leads where.
3. Repetitiveness: Items like "building the test plan" repeat themselves for no particular reason.
4. No examples: It's hard for the text to find any foundation in your mind when there are no examples to help the reader relate to. Given its monotonous descriptions, nothing could hinder the reader's efforts to understand and implement the book's ideas more than that.
The final verdict: Look for another software testing book.
Bluecliff Bluecliff
This is a very good book, despite what the other reviewers say. It is aimed at the professional software developer, consistent with good software engineering practices. Unfortunately, those who still work ad hoc in software development do not understand the value of formal processes and the resulting reduction of risk or increase in quality. This book assume that readers, and their organizations, have the required discipline to formalize their testing methods. One of the key principles in the book is that requirements must be validated and traced throughout the software life cycle - garbage in garbage out.
Consider whether or not you would like to fly in a plane or have your bank account managed by software that has not been as rigorously tested as the author requires it to be.
Dandr Dandr
The book is full of hypothesis. Till now nobody would have implemented all the checklists/templates/procedures mentioned in this book, in their real environment and I can bet on this.
Checklists are needed if the task of review/testing is very critical and the organizational processes shall demand that. An attempt to define a checklist/template to make it global is real childishness.
The definition of Verification and Validation itself is written wrong in this book. I dont know if these terms had such definitions during the past years.
Summary: We are in 2003 now. If somebody wants to go back to 1970 then this book will be very useful for them. A wise decision for normal readers would be to move away from this page. Thanks.
Whitemaster Whitemaster
Excellent book that covers testing in a lot of detail. It provides excellent ready to use test processes if you don't have any established already. Very comprehensive but you can still pick out the bits that are going to be of immediate value to your organisation. If you don't have a lot of experience you may need some help doing this though.

Highly recommended
Vizil Vizil
The Perry text will serve as a solid basic text for academic settings (thus the 4 star rating) but needs to be updated for client/server testing situations.