Book Review: 50 Quick Ideas to Improve Your Tests

LGMweb.201512.hammarberg.01They’ve done it again. Gojko Adzic, David Evans and, in this book, Tom Roden, have written another ‘50 Quick Ideas’ book. And this one is equally as good as the previous book on user stories. If not even better.

 

I got so much out of this book, and my tool belt expanded significantly. I really like the approach of these short, focused, one-topic books, starting with Gojko’s book on impact mapping. They don’t promise to be deep dives and total coverage, but rather to give you ideas (well… that’s in the title even), be challenged, and investigate further.

In this book on testing, they have divided the ideas into four groups, brushing on different aspects of testing:

  • Generating test ideas
  • Designing good checks
  • Improving testability
  • Managing large test suites

One of the things that struck me is how far (agile) testing has progressed during my relatively short period of interest in the field. This is a very sober and concrete look at the new breed of testers that want to be part in design, that takes failed tests as an opportunity to learn. We have sections on measuring test half times (how often do test change) in order to focus our testing efforts, and suggestions for how to involve and inform business users directly in the creation of key examples, etc. This is not your father’s testing… and I like it!

The early parts of this book touch more on organization of test efforts and exploratory testing, etc. There’s a lot of good things in there, but it’s not my area of expertise and interest.

The two last parts I found extremely interesting and packed with battled-hardened experiences that I sometimes found myself nodding in agreement with. And sometimes I had to reread paragraphs a few times because it was really a new take on a situation I’ve been in.

And that’s typically how you get the experiences from experts served. Some things you have experienced yourself and others are things that help your knowledge to take a jump ahead.

Everything that I didn’t know about before left me feeling that I wanted more pages on the topic. Or examples on how to implement this or that, although every Idea has a “How to make it work” section that gives you a starter.

This is by design.

The book is not meant to be a complete overview. You should, as they point out in the intro, not read this as your first book.

And, I might add: you should not read the entire book in one go. I would suggest that you browse this book for an overview and general knowledge and then use it as a tool, hands-on, in your team. Keep it next to your team, and as you run into problems, look them up in the book. There are a lot of pointers and ideas that can help you get under control many, if not all, of the testing problems I’ve seen teams run into.

I could not recommend the book more. Any serious agile tester should have this handy to be inspired to move even further.

Thank you, Neuri “Publishing” — looking forward to the next book. On retrospectives.

P.S. Were you the guys behind ‘50 Shades of Grey’ too?

This article originally appeared in the author’s blog, marcusoft.net.

 

Marcus Hammarberg

Marcus Hammarberg, the author of Kanban in Action, is a programmer, consultant and agile coach who has worked for a number of banks and insurance companies, as well as Ebay and Spotify. At present, he is especially jazzed about Node and Koa Js.

Currently, Marcus lives with his family in Indonesia, where he works for the Salvation Army.

Marcus can be reached on Twitter at @marcusoftnet.

Marcus Hammarberg
Marcus Hammarberg, the author of Kanban in Action, is a programmer, consultant and agile coach who has worked for a number of banks and insurance companies, as well as Ebay and Spotify. At present, he is especially jazzed about Node and Koa Js.

Currently, Marcus lives with his family in Indonesia, where he works for the Salvation Army.

Marcus can be reached on Twitter at @marcusoftnet.

The Related Post

This article was developed from concepts in the book Global Software Test Automation: Discussion of Software Testing for Executives. Quality cost is the sum of all costs a company invests into the release of a quality product. When developing a software product, there are 4 types of quality costs: prevention costs, appraisal costs, internal failure ...
This article was developed from concepts in the book Global Software Test Automation: Discussion of Software Testing for Executives. Introduction Metrics are the means by which the software quality can be measured; they give you confidence in the product. You may consider these product management indicators, which can be either quantitative or qualitative. They are ...
Internet-based per-use service models are turning things upside down in the software development industry, prompting rapid expansion in the development of some products and measurable reduction in others. (Gartner, August 2008) This global transition toward computing “in the Cloud” introduces a whole new level of challenge when it comes to software testing.
Experience-based recommendations to test the brains that drive the devices In essentially every embedded system there is some sort of product testing. Typically there is a list of product-level requirements (what the product does), and a set of tests designed to make sure the product works correctly. For many products there is also a set ...
Reducing the pester of duplications in bug reporting. Both software Developers and Testers need to be able to clearly identify any ‘Bug’, via the ‘Title’ used for the ‘Bug Report’.
Companies generally consider the software they own, whether it is created in-house or acquired, as an asset (something that could appear on the balance sheet). The production of software impacts the profit and loss accounts for the year it is produced: The resources used to produce the software result in costs, and methods, tools, or ...
It’s a bird! It’s a plane! It’s a software defect of epic proportions.
This article was developed from concepts in the book Global Software Test Automation: Discussion of Software Testing for Executives. Article Synopsis There are many misconceptions about Software Testing. This article deals with the 5 most common misconceptions about how Software Testing differs from other testing. Five Common Misconceptions Some of the most common misconceptions about ...
Test organizations continue to undergo rapid transformation as demands grow for testing efficiencies. Functional test automation is often seen as a way to increase the overall efficiency of functional and system tests. How can a test organization stage itself for functional test automation before an investment in test automation has even been made? Further, how ...
Most have probably heard the expression ‘less is more‘, or know of the ‘keep it simple and stupid‘ principle. These are general and well-accepted principles for design and architecture in general, and something that any software architect should aspire to. Similarly, Richard P. Gabriel (a major figure in the world of Lisp programming language, accomplished poet, and currently ...
This article was adapted from a presentation titled “How to Optimize Your Web Testing Strategy” to be presented by Hung Q. Nguyen, CEO and founder of LogiGear Corporation, at the Software Test & Performance Conference 2006 at the Hyatt Regency Cambridge, Massachusetts (November 7 – 9, 2006). Click here to jump to more information on ...
I’ve been intending to write a book review of How We Test Software At Microsoft, by Alan Page, Ken Johnston, and Bj Rollison, but for whatever reason I just never found the time, until now. In general, I like this book a lot. It’s a nice blend of the tactical and the strategic, of the ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe