Books

A practical handbook packed with real-world advice to help you write better code, adopt effective developer habits, and build great software.

Are you a VP or Head of Engineering considering the best quality engineering model for your company? Are you a director of Engineering tasked with rolling out a Quality Coach Model? Are you a test lead or software tester shifting to a quality coach role? The Quality Coach Handbook is your practical guide to shifting to a model where the whole team owns quality and in particular software engineers design, build, test and support software. Print version: Paperback and hardcover are available on Amazon. Use your country's Amazon site (e.g., Amazon.com.au for Australia) to minimise shipping time and cost.

This practical handbook provides a step-by-step guide for you to get the best continuous delivery pipeline for your software.

Are you a mobile tester looking to learn something new? Are you a software tester, developer, product manager or completely new to mobile testing? Then you should read this book as it contains lots of insights about the challenging job of a mobile tester from a practical perspective.

One of the most comprehensive no-fluff guides for software developers to help them write clean code every day. The book is packed with principles and patterns that help developers, from novices and juniors to seniors and experts, to write cleaner code.

Real-world advice for adding reliable tests to your Rails apps with RSpec, complete with expanded, exclusive content and a full sample application. Now updated for Rails 8.1! Learn to test with confidence!

Start visualizing test strategy work using Wardley maps. Take the viewpoint of your decision maker, derive guiding policies for needed decisions, and have actions that leverage change.

ウクライナ難民を支援 - 2022年5月末まで延長！ この本の売り上げの50％は、 https://unicef.hu/veszhelyzet-ukrajnaban と https://int.depaulcharity.org/fundraising-for-depaul-ukraine/ に寄付されます。 本書籍は、振る舞い駆動開発(Behavior Driven Development, BDD)や受け入れテスト駆動開発(Acceptance Test-Driven Development, ATDD)の発見フェーズを最大限に活用する方法を提供します。

Holistic testing is a comprehensive term to encompass testing throughout the development cycle from the start of an idea, through to customer interaction with a delivered feature. All members of a delivery team think about testing and quality from the beginning and throughout the cycle.  This book is about the Holistic Testing Model and how to apply it to develop a quality and testing strategy for the whole team. If you care about quality – no matter what your specialty or role in your organization is – we think you’ll find it helpful. UI/UX designers, product owners, programmers, testers, database experts, business analysts, site reliability and platform engineers, and more – this model will guide you as you collaborate to continually improve your process and product. 

A true classic, not just in computing but in the broad area of scholarship. It is partly about the philosophy and mechanisms of science; partly about designing things so they work but mostly it is about how humans view the world and create things that match that view. This book will still be worth reading for a long time to come. - Charles Ashbacher

A detailed look at the thought processes and techniques for testing a REST API based application. Starting with interactive testing using the GUI, cURL and HTTP Proxies, we move on to automating the REST API using Java and REST Assured. The case study uses an Open Source application and free and tools.

Write tests which help you add value on projects and provide a foundation of Java knowledge you can build on.

"Dear Evil Tester" contains advice that might change your test approach forever. Our reviewers said: "something completely different, "I loved it", "I couldn't put it down", "fantastic questions and answers, nothing is held back!", "I laughed - then I cried - then I laughed harder - then I cried softer", "Read it and loved it. Great book.", "full of inspirational gems", "funny and thought-provoking content". How will it affect you?

What is a good software architecture? Why should we bother structuring the code and spending time testing it? If you like spending hours debugging your programs or staying late at the office to recover from a buggy deploy in production this book is definitely NOT for you!

With the advent of LLMs and AI coding assistants, we are generating code at an ever-accelerating rate. How do we manage this influx of code without getting fatigued and overwhelmed? How do we ensure coding standards are maintained? What practices and tools can we put in place to amplify our efforts while not introducing more bugs?