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

There are many ways to approach test design. These approaches range from checklists to very precise algorithms in which test conditions are combined to achieve the most efficiency in testing. There are situations, such as in testing mobile applications, complex systems and cyber security, where tests need to be creative, cover a lot of functionality, ...
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 ...
Jeff Offutt – Professor of Software Engineering in the Volgenau School of Information Technology at George Mason University – homepage – and editor-in-chief of Wiley’s journal of Software Testing, Verification and Reliability, LogiGear: How did you get into software testing? What do you find interesting about it? Professor Offutt: When I started college I didn’t ...
Introduction Keyword-driven testing is a software testing technique that separates much of the programming work of test automation from the actual test design. This allows tests to be developed earlier and makes the tests easier to maintain. Some key concepts in keyword driven testing include:
LogiGear Magazine March Issue 2021: Metrics & Measurements: LogiGear’s Guide to QA Reporting and ROI
With this edition of LogiGear Magazine, we introduce a new feature, Mind Map. A mind map is a diagram, usually devoted to a single concept, used to visually organize related information, often in a hierarchical or interconnected, web-like fashion. This edition’s mind map, created by Sudhamshu Rao, focuses on tools that are available to help ...
MARCH 2016_ TEST DESIGN ISSUE
VISTACON 2010 – Keynote: The future of testing THE FUTURE OF TESTING BJ Rollison – Test Architect at Microsoft VISTACON 2010 – Keynote   BJ Rollison, Software Test Architect for Microsoft. Mr. Rollison started working for Microsoft in 1994, becoming one of the leading experts of test architecture and execution at Microsoft. He also teaches ...
One of the most dreaded kinds of bugs are the ones caused by fixes of other bugs or by code changes due to feature requests. I like to call these the ‘bonus bugs,’ since they come on top on the bug load you already have to deal with. Bonus bugs are the major rationale for ...
Differences in interpretation of requirements and specifications by programmers and testers is a common source of bugs. For many, perhaps most, development teams the terms requirement and specification are used interchangeably with no detrimental effect. In everyday development conversations the terms are used synonymously, one is as likely to mean the “spec” as the “requirements.”
Introduction Software Testing 3.0 is a strategic end-to-end framework for change based upon a strategy to drive testing activities, tool selection, and people development that finally delivers on the promise of Software Testing. For more details on the evolution of Software Testing and Software Testing 3.0 see: The Early Evolution of Software Testing Software Testing ...
At VISTACON 2011, Jane sat down with LogiGear Sr. VP, Michael Hackett, to discuss complex systems.

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe