An updated version of the bestselling, "Game Testing All In One", this book equips the reader with the rationale for vigorous testing of game software, how game testing and the tester fit into the game development process, practical knowledge of tools to apply to game testing, game tester roles and responsibilities, and the measurements to determine game quality and testing progress. The reader is taken step-by-step through test design and other QA methods, using real game situations. The book includes content for the latest console games and the new crop of touch, mobile, and social games that have recently emerged. A companion DVD contains the tools used for the examples in the book and additional resources such as test table templates and generic flow diagrams to get started quickly with any game test project. Each chapter includes questions and exercises, making the book suitable for classroom use as well as a personal study or reference tool.
Game Testing All in One Second Edition
and over 1.5 million other books are available for Amazon Kindle . Learn more
| ||||||||||||||||||
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Visit the Books Trade-In Store for more details. Learn more. |
Book Description
Product details
Would you like to update product info or give feedback on images?
|
More About the Author
Discover books, learn about writers, and more.
Inside This Book
(Learn More)
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
Most Helpful Customer Reviews
4 of 5 people found the following review helpful
By Stoofer
Format:Paperback
...that could bring the general level of maturity from the wider software testing community to the industry. This book isn't it.
As a seasoned games veteran, I was looking for some useful tips in this book. It's asinie metaphors, diagrams and language was an immediate turn-off. This book is not aimed at a professional tester and tries far too hard to be 'cool'. The authors have appeared to make no attempt to clarify terminology used in their own shops and often stray wildly from ISTQB testing terms... and also stray from official hardware terminology for systems such as the Xbox.
Many examples are misleading, and the author appears to have no problems telling the tester to adopt a completely, illogically, contradictory approach to a build. Several procedures are written in the wrong order...
In short, a stab at filling a need for a games testing bible, but a stab that misses the target. Your daughter might enjoy laughing at the pictures while you laugh at the statement that 'some games may take months to develop'.
As a seasoned games veteran, I was looking for some useful tips in this book. It's asinie metaphors, diagrams and language was an immediate turn-off. This book is not aimed at a professional tester and tries far too hard to be 'cool'. The authors have appeared to make no attempt to clarify terminology used in their own shops and often stray wildly from ISTQB testing terms... and also stray from official hardware terminology for systems such as the Xbox.
Many examples are misleading, and the author appears to have no problems telling the tester to adopt a completely, illogically, contradictory approach to a build. Several procedures are written in the wrong order...
In short, a stab at filling a need for a games testing bible, but a stab that misses the target. Your daughter might enjoy laughing at the pictures while you laugh at the statement that 'some games may take months to develop'.
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com:
5.0 out of 5 stars
2 reviews
15 of 16 people found the following review helpful
5.0 out of 5 stars
Why Game Testing All In One is a Must!
3 April 2005
By Donald Costello
- Published on Amazon.com
Format:Paperback
Traditional program testing has come a long way in 50 years but the complexity, time constraints and variety of situations facing game testers is at the edge of the software testing world.
The authors combine authentic experience with Computer Games and Game Testing in a logical, pragmatic and interesting way. They long ago reasoned that it is very costly (if not sometimes impossible) to test all possible paths through a game's options and through the application of some insightful statistical approaches present ways to reduce the total number of tests required under certain assumptions. To me this one insight was worth the cost of the book.
Beyond this outstanding statistical testing insight for the workers in the field, the expository material that covers Games is exceptionally good for the individual trying to put the whole field in perspective. In Part I they address "Being a Game Tester" (with a side venture later in the book to identify different game testing personalities) followed by a good discussion of "Why Testing is Important". Part II talks about the "Making of a Game" while Part III introduces the concepts and vocabulary of Testing. In Part IV the authors bring in the concept of Combinatorial Testing ( another statistical approach) and present it in a step by step way so that the tester can perform the testing suite without knowing all of the theory behind that approach. "Test Flow Diagrams", "Cleanroom Testing" and "Test Trees" adds very modern disciplined techniques to the testing tool process that will prove of value. Part V discusses some advanced testing ideas all of which are very practical in the fast evolving world of Games.
The authors seem to have been brought together and inspired to write just at the time when the field realizes that loosely structured ad-hoc testing may be costing more than the field can afford.
The authors combine authentic experience with Computer Games and Game Testing in a logical, pragmatic and interesting way. They long ago reasoned that it is very costly (if not sometimes impossible) to test all possible paths through a game's options and through the application of some insightful statistical approaches present ways to reduce the total number of tests required under certain assumptions. To me this one insight was worth the cost of the book.
Beyond this outstanding statistical testing insight for the workers in the field, the expository material that covers Games is exceptionally good for the individual trying to put the whole field in perspective. In Part I they address "Being a Game Tester" (with a side venture later in the book to identify different game testing personalities) followed by a good discussion of "Why Testing is Important". Part II talks about the "Making of a Game" while Part III introduces the concepts and vocabulary of Testing. In Part IV the authors bring in the concept of Combinatorial Testing ( another statistical approach) and present it in a step by step way so that the tester can perform the testing suite without knowing all of the theory behind that approach. "Test Flow Diagrams", "Cleanroom Testing" and "Test Trees" adds very modern disciplined techniques to the testing tool process that will prove of value. Part V discusses some advanced testing ideas all of which are very practical in the fast evolving world of Games.
The authors seem to have been brought together and inspired to write just at the time when the field realizes that loosely structured ad-hoc testing may be costing more than the field can afford.
5.0 out of 5 stars
Sorely needed text on game testing
27 April 2012
By technicat
- Published on Amazon.com
Format:Kindle Edition|Amazon Verified Purchase
There's no shortage of books on the sexy aspects of game development - design, art, programming, business - but hardly any on testing, which is an integral part of a game project. Keep in mind, it's much more likely for a company to have a full-time testing staff all the way through the project than audio designers or writers. So you might find this long and comprehensive text a bit dry, but it is important. It explains the importance of testing, explains various methodical techniques to provide test coverage and makes the subject a bit more interesting by citing examples of real games. I thought I pretty much knew everything about this subject, but I did learn one thing that now seems obviously useful - having separate priority and severity labels for each bug report in a bug database (a peeve of mine is that severities are often altered or bugs even in accurately marked closed to make the numbers look good - "juking the stats" as they say in The Wire). If I had to list some areas of improvement, I'd say the initial definition of regression testing didn't sound quite right to me and it's still not clear to me how to implement proper regression testing. And as a programmer, the explanations of coding bugs sound a bit weird to me (also, there's one additional bug category I could supply from personal experience - bugs that show up in release builds but not developer builds because there's "safer" compilation in the latter). But until there's some competition, this should be the standard reference.
›
Go to Amazon.com to see both reviews
5.0 out of 5 stars
Were these reviews helpful?
Let us know
Listmania!
Look for similar items by category
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
