Exploratory Software Testing Tips by Whittaker James (33 results)

Condition: Very Good. Item in very good condition! Textbooks may not include supplemental items i.e. CDs, access codes etc.

Condition: very_good. Fast Free Shipping â" Very Good condition book with a firm cover and clean pages. Shows normal use and some light wear or limited notes markings. A solid, nice copy to enjoy.

Paperback. Condition: Very Good. How to Find and Fix the Killer Software Bugs that Evade Conventional Testing   In Exploratory Software Testing, renowned software testing expert James Whittaker reveals the real causes of today?s most serious, well-hidden software bugs--and introduces powerful new ?exploratory? techniques for finding and correcting them.   Drawing on nearly two decades of experience working at the cutting edge of testing with Google, Microsoft, and other top software organizations, Whittaker introduces innovative new processes for manual testing that are repeatable, prescriptive, teachable, and extremely effective. Whittaker defines both in-the-small techniques for individual testers and in-the-large techniques to supercharge test teams. He also introduces a hybrid strategy for injecting exploratory concepts into traditional scripted testing. You?ll learn when to use each, and how to use them all successfully.   Concise, entertaining, and actionable, this book introduces robust techniques that have been used extensively by real testers on shipping software, illuminating their actual experiences with these techniques, and the results they?ve achieved. Writing for testers, QA specialists, developers, program managers, and architects alike, Whittaker answers crucial questions such as:   ?  Why do some bugs remain invisible to automated testing--and how can I uncover them? ?  What techniques will help me consistently discover and eliminate ?show stopper? bugs? ?  How do I make manual testing more effective--and less boring and unpleasant? ?  What?s the most effective high-level test strategy for each project? ?  Which inputs should I test when I can?t test them all? ?  Which test cases will provide the best feature coverage? ?  How can I get better results by combining exploratory testing with traditional script or scenario-based testing? ?  How do I reflect feedback from the development process, such as code changes.…

Condition: Very Good. Pages intact with possible writing/highlighting. Binding strong with minor wear. Dust jackets/supplements may not be included. Stock photo provided. Product includes identifying sticker. Better World Books: Buy Books. Do Good.

Condition: Good. Pages intact with minimal writing/highlighting. The binding may be loose and creased. Dust jackets/supplements are not included. Stock photo provided. Product includes identifying sticker. Better World Books: Buy Books. Do Good.

Condition: Very Good. Very Good condition. A copy that may have a few cosmetic defects. May also contain light spine creasing or a few markings such as an owner's name, short gifter's inscription or light stamp.

Paperback. Condition: Good. Connecting readers with great books since 1972! Used textbooks may not include companion materials such as access codes, etc. May have some wear or writing/highlighting. We ship orders daily and Customer Service is our top priority.

Paperback. Condition: As New. No Jacket. Pages are clean and are not marred by notes or folds of any kind. ~ ThriftBooks: Read More, Spend Less.

Paperback. Condition: Fair. No Jacket. Readable copy. Pages may have considerable notes/highlighting. ~ ThriftBooks: Read More, Spend Less.

Paperback. Condition: Fair. No Jacket. Readable copy. Pages may have considerable notes/highlighting. ~ ThriftBooks: Read More, Spend Less.

Paperback. Condition: Very Good. No Jacket. May have limited writing in cover pages. Pages are unmarked. ~ ThriftBooks: Read More, Spend Less.

Paperback. Condition: Fair. No Jacket. Readable copy. Pages may have considerable notes/highlighting. ~ ThriftBooks: Read More, Spend Less.

Paperback. Condition: Very Good. No Jacket. May have limited writing in cover pages. Pages are unmarked. ~ ThriftBooks: Read More, Spend Less.

Paperback. Condition: Good. No Jacket. Pages can have notes/highlighting. Spine may show signs of wear. ~ ThriftBooks: Read More, Spend Less.

Paperback. Condition: Very Good. No Jacket. May have limited writing in cover pages. Pages are unmarked. ~ ThriftBooks: Read More, Spend Less.

Paperback. Condition: Very Good. The book has been read, but is in excellent condition. Pages are intact and not marred by notes or highlighting. The spine remains undamaged.

paperback. Condition: Good. Most items will be dispatched the same or the next working day. A copy that has been read but remains in clean condition. All of the pages are intact and the cover is intact and the spine may show signs of wear. The book may have minor markings which are not specifically mentioned.…

paperback. Condition: Very Good. Most items will be dispatched the same or the next working day. A copy that has been read, but is in excellent condition. Pages are intact and not marred by notes or highlighting. The spine remains undamaged.

Paperback. Condition: Very Good. Shipped within 24 hours from our UK warehouse. Clean, undamaged book with no damage to pages and minimal wear to the cover. Spine still tight, in very good condition. Remember if you are not happy, you are covered by our 100% money back guarantee.

Condition: very good. Gut/Very good: Buch bzw. Schutzumschlag mit wenigen Gebrauchsspuren an Einband, Schutzumschlag oder Seiten. / Describes a book or dust jacket that does show some signs of wear on either the binding, dust jacket or pages.

Condition: New.

Condition: New. In English.

Condition: New. 2009. 1st Edition. Paperback. Num Pages: 256 pages, Illustrations. BIC Classification: UMZT. Category: (P) Professional & Vocational. Dimension: 231 x 180 x 15. Weight in Grams: 416. . . . . .

Paperback / softback. Condition: New. New copy - Usually dispatched within 4 working days.

Condition: New. 2009. 1st Edition. Paperback. Num Pages: 256 pages, Illustrations. BIC Classification: UMZT. Category: (P) Professional & Vocational. Dimension: 231 x 180 x 15. Weight in Grams: 416. . . . . . Books ship from the US and Ireland.

Paperback. Condition: Brand New. 1st edition. 256 pages. 9.00x7.00x0.70 inches. In Stock.

Paperback. Condition: Brand New. 1st edition. 256 pages. 9.00x7.00x0.70 inches. In Stock. This item is printed on demand.

Taschenbuch. Condition: Neu. This item is printed on demand - it takes 3-4 days longer - Neuware -How to Find and Fix the Killer Software Bugs that Evade Conventional Testing In Exploratory Software Testing, renowned software testing expert James Whittaker reveals the real causes of today s most serious, well-hidden software bugs--and introduces powerful new exploratory techniques for finding and correcting them. Drawing on nearly two decades of experience working at the cutting edge of testing with Google, Microsoft, and other top software organizations, Whittaker introduces innovative new processes for manual testing that are repeatable, prescriptive, teachable, and extremely effective. Whittaker defines both in-the-small techniques for individual testers and in-the-large techniques to supercharge test teams. He also introduces a hybrid strategy for injecting exploratory concepts into traditional scripted testing. You ll learn when to use each, and how to use them all successfully. Concise, entertaining, and actionable, this book introduces robust techniques that have been used extensively by real testers on shipping software, illuminating their actual experiences with these techniques, and the results they ve achieved. Writing for testers, QA specialists, developers, program managers, and architects alike, Whittaker answers crucial questions such as: Why do some bugs remain invisible to automated testing--and how can I uncover them What techniques will help me consistently discover and eliminate show stopper bugs How do I make manual testing more effective--and less boring and unpleasant What s the most effective high-level test strategy for each project Which inputs should I test when I can t test them all Which test cases will provide the best feature coverage How can I get better results by combining exploratory testing with traditional script or scenario-based testing How do I reflect feedback from the development process, such as code changes 256 pp. Englisch.…

Taschenbuch. Condition: Neu. nach der Bestellung gedruckt Neuware - Printed after ordering - How to Find and Fix the Killer Software Bugs that Evade Conventional Testing In Exploratory Software Testing, renowned software testing expert James Whittaker reveals the real causes of today s most serious, well-hidden software bugs--and introduces powerful new exploratory techniques for finding and correcting them. Drawing on nearly two decades of experience working at the cutting edge of testing with Google, Microsoft, and other top software organizations, Whittaker introduces innovative new processes for manual testing that are repeatable, prescriptive, teachable, and extremely effective. Whittaker defines both in-the-small techniques for individual testers and in-the-large techniques to supercharge test teams. He also introduces a hybrid strategy for injecting exploratory concepts into traditional scripted testing. You ll learn when to use each, and how to use them all successfully. Concise, entertaining, and actionable, this book introduces robust techniques that have been used extensively by real testers on shipping software, illuminating their actual experiences with these techniques, and the results they ve achieved. Writing for testers, QA specialists, developers, program managers, and architects alike, Whittaker answers crucial questions such as: Why do some bugs remain invisible to automated testing--and how can I uncover them What techniques will help me consistently discover and eliminate show stopper bugs How do I make manual testing more effective--and less boring and unpleasant What s the most effective high-level test strategy for each project Which inputs should I test when I can t test them all Which test cases will provide the best feature coverage How can I get better results by combining exploratory testing with traditional script or scenario-based testing How do I reflect feedback from the development process, such as code changes. …

Taschenbuch. Condition: Neu. This item is printed on demand - Print on Demand Titel. Neuware -How to Find and Fix the Killer Software Bugs that Evade Conventional Testing In Exploratory Software Testing, renowned software testing expert James Whittaker reveals the real causes of today's most serious, well-hidden software bugs--and introduces powerful new "exploratory" techniques for finding and correcting them. Drawing on nearly two decades of experience working at the cutting edge of testing with Google, Microsoft, and other top software organizations, Whittaker introduces innovative new processes for manual testing that are repeatable, prescriptive, teachable, and extremely effective. Whittaker defines both in-the-small techniques for individual testers and in-the-large techniques to supercharge test teams. He also introduces a hybrid strategy for injecting exploratory concepts into traditional scripted testing. You'll learn when to use each, and how to use them all successfully. Concise, entertaining, and actionable, this book introduces robust techniques that have been used extensively by real testers on shipping software, illuminating their actual experiences with these techniques, and the results they've achieved. Writing for testers, QA specialists, developers, program managers, and architects alike, Whittaker answers crucial questions such as: Why do some bugs remain invisible to automated testing--and how can I uncover them What techniques will help me consistently discover and eliminate "show stopper" bugs How do I make manual testing more effective--and less boring and unpleasant What's the most effective high-level test strategy for each project Which inputs should I test when I can't test them all Which test cases will provide the best feature coverage How can I get better results by combining exploratory testing with traditional script or scenario-based testing How do I reflect feedback from the development process, such as code changes Financial Times Prent., St.-Martin-Straße 82, 81541 München 256 pp. Englisch.…