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

March Issue 2019: Leading the Charge with Better Test Methods
At VISTACON 2011, Jane sat down with LogiGear Sr. VP, Michael Hackett, to discuss complex systems.
In software testing, we need to devise an approach that features a gradual progression from the simplest criteria of testing to more sophisticated criteria. We do this via many planned and structured steps, each of which brings incremental benefits to the project as a whole. By this means, as a tester masters each skill or area ...
With complex software systems, you can never test all of the functionality in all of the conditions that your customers will see. Start with this as a fact: You will never test enough! Step 2 in getting started is to read and re-read The Art of Software Testing by Glenford Myers. This classic will set the ...
Alexa Voice Service (AVS): Amazon’s service offering for a voice-controlled AI assistant. Offered in different products. Source: https://whatis.techtarget.com/definition/Alexa-Voice-Services-AVS Autopilot Short for “automatic pilot,” a device for keeping an aircraft on a set course without the intervention of the pilot. Source: https://en.oxforddictionaries.com/definition/us/automatic_pilot Blockchain Infrastructure: A complex, decentralized architecture that orchestrates many systems running asynchronously over the ...
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’.
LogiGear Magazine March Issue 2021: Metrics & Measurements: LogiGear’s Guide to QA Reporting and ROI
Back from more training, I was up at a client in Bellevue and really enjoyed teaching a performance class to a world class testing organization. I found that the students were very receptive to many of the concepts and ideas that the class offers.
In today’s mobile-first world, a good app is important, meaning an effective Mobile Testing strategy is  essential.  
When it is out of the question to delay delivery, the solution is a prioritization strategy in order to do the best possible job within the time constraints. The scenario is as follows: You are the test manager. You made a plan and a budget for testing. Your plans were, as far as you know, ...
From cross-device testing, to regression testing, to load testing, to data-driven testing, check out the types of testing that are suitable for Test Automation. Scene: Interior QA Department. Engineering is preparing for a final product launch with a deadline that is 12 weeks away. In 6 weeks, there will be a 1 week quality gate, ...
This is an adaptation of a presentation entitled Software Testing 3.0 given by Hung Nguyen, LogiGear CEO, President, and Founder. The presentation was given as the keynote at the Spring 2007 STPCON conference in San Mateo, California. Watch for an upcoming whitepaper based on this topic. Introduction This first article of this two article series ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe