James A. Whittaker Books

James A. Whittaker is a renowned author and computer scientist. With a background in academia and industry, he has made significant contributions to the field of software testing. Whittaker has written several influential books on software testing, including "Exploratory Software Testing". His work focuses on exploring new approaches to testing and finding innovative ways to improve software quality. Whittaker's expertise and practical insights have made him a leading figure in the software testing community.

How do we create content on this page?
1
 Books: Exploratory Software Testing by James A. Whittaker

Exploratory Software Testing

James A. Whittaker

What's Exploratory Software Testing about?

Exploratory Software Testing by James A. Whittaker is a comprehensive guide to the principles and techniques of exploratory testing. It provides practical insights into how to approach testing in an exploratory manner, emphasizing the importance of creativity and adaptability in uncovering software defects. The book offers valuable advice for testers and developers looking to improve their testing practices.

Who should read Exploratory Software Testing?

  • Software testers who want to improve their testing skills

  • Quality assurance professionals looking to enhance their testing processes

  • Developers who want to understand the importance of exploratory testing


2
 Books: How to Break Software by James A. Whittaker

How to Break Software

James A. Whittaker

What's How to Break Software about?

How to Break Software by James A. Whittaker delves into the art of finding and fixing software defects. Through real-world examples and practical advice, the book offers a unique perspective on software testing, challenging traditional methods and providing innovative techniques to uncover hidden bugs. It is a must-read for anyone involved in software development and quality assurance.

Who should read How to Break Software?

  • Software testers who want to improve their skills and learn new techniques

  • Developers who want to understand how their code can be broken and how to prevent it

  • Quality assurance professionals who want to enhance their testing processes