Buying Options

Kindle Price: $9.99

You've subscribed to ! We will preorder your items within 24 hours of when they become available. When new books are released, we'll charge your default payment method for the lowest price available during the pre-order period.

Update your device or payment method, cancel individual pre-orders or your subscription at
Your Memberships & Subscriptions

There was an error. We were unable to process your subscription due to an error. Please refresh and try again.

Enter a promotion code or Gift Card

Share <Embed>

Fifty Quick Ideas To Improve Your Tests by [Gojko Adzic, David Evans, Tom Roden, Nikola Korac]

Follow the Authors

See all

Gojko Adzic

David Evans

Fifty Quick Ideas To Improve Your Tests Kindle Edition

by Gojko Adzic (Author), David Evans (Author), Tom Roden (Author), Format: Kindle Edition

66 ratings

See all formats and editions

Price

New from

Used from

Kindle

"Please retry"

$9.99

—

Paperback

"Please retry"

$26.62

$21.39

$17.81

This book is for cross-functional teams working in an iterative delivery environment, planning with user stories and testing frequently changing software under tough time pressure. This book will help you test your software better, easier and faster. Many of these ideas also help teams engage their business stakeholders better in defining key expectations and improve the quality of their software products.

Print length

222 pages
Language

English
Publication date

May 18, 2015
File size

10674 KB
Page Flip

Enabled
Word Wise

Not Enabled
Enhanced typesetting

Enabled
See all details

Due to its large file size, this book may take longer to download

Gojko Adzic
217
Kindle Edition
1 offer from $9.99
Gojko Adzic
359
Kindle Edition
1 offer from $9.99
Tom Roden
56
Kindle Edition
1 offer from $9.99
Gojko Adzic
51
Kindle Edition
1 offer from $9.99
Gojko Adzic
77
Kindle Edition
1 offer from $38.99
Bret Pettichord
198
Kindle Edition
1 offer from $32.00

Product details

ASIN ‏ : ‎ B00XVFFK7E
Publisher ‏ : ‎ Neuri Consulting LLP (May 18, 2015)
Publication date ‏ : ‎ May 18, 2015
Language ‏ : ‎ English
File size ‏ : ‎ 10674 KB
Simultaneous device usage ‏ : ‎ Unlimited
Text-to-Speech ‏ : ‎ Enabled
Screen Reader ‏ : ‎ Supported
Enhanced typesetting ‏ : ‎ Enabled
X-Ray ‏ : ‎ Not Enabled
Word Wise ‏ : ‎ Not Enabled
Print length ‏ : ‎ 222 pages
Lending ‏ : ‎ Enabled

Best Sellers Rank: #790,631 in Kindle Store (See Top 100 in Kindle Store)
- #404 in Web Programming
- #459 in Software Testing
- #732 in Software Development (Kindle Store)

Customer Reviews:
66 ratings

About the authors

Follow authors to get new release updates, plus improved recommendations.

Gojko Adzic
Brief content visible, double tap to read full content.
Full content visible, double tap to read brief content.
Gojko Adzic is a partner at Neuri Consulting LLP. He one of the 2019 AWS Serverless Heroes, the winner of the 2016 European Software Testing Outstanding Achievement Award, and the 2011 Most Influential Agile Testing Professional Award. Gojko’s book Specification by Example won the Jolt Award for the best book of 2012, and his blog won the UK Agile Award for the best online publication in 2010.
Gojko is a frequent speaker at software development conferences and one of the authors of MindMup and Claudia.js.
As a consultant, Gojko has helped companies around the world improve their software delivery, from some of the largest financial institutions to small innovative startups. Gojko specialises in are agile and lean quality improvement, in particular impact mapping, agile testing, specification by example and behaviour driven development.
See more on the author's page
David Evans
Brief content visible, double tap to read full content.
Full content visible, double tap to read brief content.
David Evans is an Agile Software Development coach. He provides training, strategic consulting and team coaching in the field of Agile Quality, Specification By Example, Behaviour Driven Development and Agile Product Management. Born and brought up in Australia, David currently lives and works in the UK.
See more on the author's page
Tom Roden
Brief content visible, double tap to read full content.
Full content visible, double tap to read brief content.
Tom Roden is a software delivery consultant, coach and quality enthusiast, helping teams and people make the changes needed to successfully adapt to the changing demands of their environment.
He helps teams deliver business impacts through the rapid delivery of high quality software, supporting ongoing improvement through process and practice refinement, influenced by agile and lean principles.
Tom specialises in transformation, coaching, large scale agile implementation and testing, from test management and strategy, through to practitioner approaches such as specification by example, BDD and context driven testing.
He is author of the books Fifty Quick Ideas to Improve your Tests and Fifty Quick Ideas to improve your Retrospectives
See more on the author's page

Customer reviews

5 star		69%
4 star		20%
3 star		5%
2 star		4%
1 star		3%

How customer reviews and ratings work

Top reviews from the United States

There was a problem filtering reviews right now. Please try again later.

Dima

Waste of time

Reviewed in the United States on January 31, 2020

Verified Purchase

This is opinion of person with 7+ yars of experience in QA. It's up to you to ignore it or no.

This book probably will be helpful if you have a year of experience in QA and you have never learned basics. It doesn't give principles it really just give some ideas. And these ideas , from my point of view, can often lead to other problems

If you at least know that team should not touch code until they really Understand Why they are implementing this - then you probably can just ignore around 15 'ideas' from this book.
If you are not skipping planning phase you probably can skip another 5 'ideas'.

Even more, if you don't have 5+ years of experience it's better to just not read some ideas. And if you have - you will probably waste your time.
For example 'writing assertion first'. Yes idea looks nice. You are covering all results and after that you are covering all inputs which lead to these results. Do you see a problem in my statement? Most of the newer testers will not see it. Most of newer testers will only try bunch of inputs which would lead to expected results. They will not try to send broken or large file, or file with different encoding. Why? Because they don't know what will be the output!

Or there was some idea about partitioning. I don't think that it was mentioned that you should talk to dev team (or check code). As author is saying similar inputs can lead to different results. But to be frank sitting in groups and discussing partitions (keep in mind you need at least 4 testers for this) wastes quite a lot of time. If you ask about data flow and checks in code you will not only understand better edge cases but also what was already covered on unit level. And again - I was taught about this in my first month. Just work as a team. Work with developers and BAs. They are your friends

Also some ideas like 'one test one topic' are just covering some super basic rules in roundabout way. Just test one thing in one test. It's one of the main rules when creating TC

One person found this helpful

Helpful

Marcus Hammarberg

Read it, keep it close, use it!

Reviewed in the United States on May 29, 2015

Verified Purchase

They’ve done it again. Gojko Adzic, David Evans and, in this book, Tom Roden has written another 50 quick ideas book. And this one is equally good as the previous book on user stories. If not even better. This is my review after reading the book in the worst possible manner. I’ll tell you why. But even doing so I got so much out of this book and my tool belt expanded significantly.

I really like the approach of these short, focus, one-topic books, starting with Gojoks 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 4 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 have progress during my relative short period interested 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, there’s suggestions for how to involve and inform business users directly in creation of key examples etc. This is not your fathers testing and I like it!

I have a confession to make: I’m not really into testing. I’m a developer and very fascinated by agile testing but the early parts of this book touch more on organizations of test efforts and exploratory testing planning etc. That’s not my thing really. I read those parts faster. There’s a lot of good things in there, let there be no mistake about that, but it’s not my area of expertise and interest.

The two last parts I found extremely interesting and packed with battled-harden experiences that I sometimes found myself nodding in agreement too. Sometimes I heard myself going “Aaaaaah - I’ve never thought about that”. 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. Somethings you have experienced yourself and other things is things that helps your knowledge to take a jump ahead.

The only real complaint you could have on this book is around the format. Yes I know. That’s what I said that I loved. I’m an enigma, what can I say?

Everything that I didn’t know about before left me feeling that I wanted some pages more on the topic. Or examples on how to implement this, 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. I might add: you should not read the entire book in one go. This is what I did. It left me hugely inspired to try things out, but also a little bit overwhelmed and scared that I will forget everything I read.

Instead I would suggest that you browse this book for overview and knowledge and then use it as a tool, hands-on, in your team. Keep it next to your team and look problems you run into up in the book. There’s a lot of pointers and ideas that can help you to get many, if not all, of the testing problems I’ve seen team run into under control.

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

3 people found this helpful

Helpful

Mike P

Agile Skill Refinement

Reviewed in the United States on February 6, 2019

Verified Purchase

This is the third book I’ve bought from this series. Agile is easy to understand, but difficult to do well. These books help. The book was a great price. The book was advertised as very good used condition, but it looked like it was never used new condition. I’m very happy with my purchase and service I received.

Helpful

Jim Holmes

Great addition to any team's library!

Reviewed in the United States on November 2, 2015

Verified Purchase

This really is a terrific, must-have book for teams (NOT JUST TESTERS!) trying to improve how they work with testing. Lots of great tips in here from data to flows to specifications. I love that Gojko's kept the ideas short and concise. It's easy to use this book as a guide for ongoing training, lunch and learns, etc.

2 people found this helpful

Helpful

AmazonSlime

Good But Not Great

Reviewed in the United States on December 15, 2015

Verified Purchase

Decent book, illustrations keep testing talk fun and engaging. As a CDT (context driven testing) tester, I would recommend this as a fun book to read, but not essential. Good testing is about a mindset shift, that fuels a process shift, not the other way around. Test cases are fine if you need them for a legal reason to satisfy a compliance requirement, but I would have liked to see this book focus more on test strategy. I would recommend people start with James Bach's book first called "Lessons Learned in Software Testing", then "Thinking Fast And Slow" by Daniel Khaneman, then buy this book after absorbing those two first.

6 people found this helpful

Helpful

Masa K. Maeda

The best complement to agile testing books

Reviewed in the United States on March 24, 2016

Verified Purchase

The best complement to agile testing books. This is a 100% practical approach to eliminating testing and quality headaches. It is very well organized and fun to read. You can start improving your Testing in less than 10 minutes from opening this book (I did).

One person found this helpful

Helpful

S. Conlin

A must have book for QA professsionals.

Reviewed in the United States on November 23, 2015

Verified Purchase

This book features concise suggestions along with examples of common mistakes and tips on how to implement the changes. While I was familiar with most of the concepts being presented I found the explanations provided to be very helpful in finding ways of passing information on to teammates. I recommend this book for any and all QA professsionals.

Helpful

Top reviews from other countries

Mihai Bojin

Good testing ideas!

Reviewed in the United Kingdom on December 29, 2016

Verified Purchase

Packed with useful advice, in a very easy to digest format.

One person found this helpful

Liz76

Five Stars

Reviewed in the United Kingdom on August 13, 2015

Verified Purchase

Great tips in this book, very readable, well laid out and backed up with examples.

One person found this helpful

Angelo F.

Useful for all QA

Reviewed in Italy on June 15, 2018

Verified Purchase

Great book. Easy and simple. It gives a good way to understand and improve testing. Bought also after some coworkers were happy to read it

Ashman

Every tester should read this!

Reviewed in Canada on November 29, 2017

Verified Purchase

Fantastic book, distilling years of experience and practice into instantly understandable and actionable changes that will definitely improve your testing and the practices of your team.

Sid

Four Stars

Reviewed in Canada on May 4, 2018

Verified Purchase

Excellent knowledge shared. Very creative and applicable ideas presented which are very practical to implement.

See all reviews