Legal Consequences of Defective Software. This is a standard QA reference book for a reason. Want to Read saving…. CEM KANER consults on technical and software development management issues and teaches about software testing at local universities and at several software companies. Jun 02, Adib rated it it was amazing. Probably a bit outdated, but I think the principles are still applicable. The authors have all been test managers and software development managers at well-known Silicon Valley software companies.
Uploader: | Shakamuro |
Date Added: | 10 April 2009 |
File Size: | 32.68 Mb |
Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
Downloads: | 55487 |
Price: | Free* [*Free Regsitration Required] |
This is a dummy description. Is it the most useful book out there? Trivia About Testing Computer Aug 28, Coral Rose rated it it was ok Shelves: The problem tracking system 87 The prime objective of a problem tracking system 90 The tasks of the system 90 Problem tracking overview 90 The users of the tracking system 97 Mechanics of the database Further thoughts on problem reporting Glossary 7. Independent test agencies Scheduling tips Your staff Appendix: Request permission to reuse content from this site.
Solid information, but very dated examples. I read this book because it came highly recommended by many other testers in the industry. Reporting and Analyzing Bugs.
Kanfr Example Test Series. One of the great software testing books. The Objectives and Limits of Testing. Ludmila Ekzamengirl rated it it was amazing Nov 14, I thought it would not be relevant for Web and mobile testing, but the principles are timeless.
Testing Computer Software
Thorough explanation of motivation, challenges, and terminology. This book will teach you how to test computer software under real-world conditions.
The information in this book is extremely useful for anyone in the software testing business. Prior to his professorship, Kaner worked in the software industry beginning in in Silicon Valley "as computr tester, programmer, tech writer, software development manager, product development director, and independent software development consultant. Permissions Request permission to reuse content from this site. It's just that better work has been done since.
Tying it together Software development tradeoffs Software development models Quality-related costs The development time line Product design Fragments coded: However, I was really hoping this book would actually have shown more code, both in the sense of the testing code, and the code that's being tested.
Would you like to 2nf to the site? Chris Martin rated it liked it Feb 20, Feb 26, Sergey Badulin aoftware it really liked it. The book explains the testing side of that success.
You are currently using the site but have requested a page in the site. Test Planning and Test Documentation.
Testing Computer Software by Cem Kaner
More than that, it's because those chapters are really, really long. Laxminarayan rated it really liked it Jan 17, An example test series 1 The first cycle of testing 1 The second cycle of testing 11 What editiln happen in later cycles of testing 16 2.
Testing Printers and other devices.
Want to Read Currently Reading Read. Test case design Characteristics of a good test Equivalence classes and boundary values Visible state transitions Race conditions and other time dependencies Load testing Error guessing Function equivalence testing: Added to Your Shopping Cart.
No comments:
Post a Comment