Your memberships & subscriptions
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet or computer—no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera, scan the code below and download the Kindle app.
Fifty Quick Ideas To Improve Your Tests Kindle Edition
- LanguageEnglish
- Publication date18 May 2015
- File size10674 KB
Product details
- ASIN : B00XVFFK7E
- Publisher : Neuri Consulting LLP (18 May 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 : 236 pages
- Best Sellers Rank: 758,572 in Kindle Store (See Top 100 in Kindle Store)
- 419 in Software Development (Kindle Store)
- 425 in Software Testing
- 1,482 in Web Programming
- Customer Reviews:
About the authors
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.
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.
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
Customer reviews
Top reviews from Australia
Top reviews from other countries
- AshmanReviewed in Canada on 29 November 2017
5.0 out of 5 stars Every tester should read this!
Verified PurchaseFantastic 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.
- Marcus HammarbergReviewed in the United States on 29 May 2015
5.0 out of 5 stars Read it, keep it close, use it!
Verified PurchaseThey’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.