Fifty Quick Ideas To Improve Your Tests
- Downloads：2051
- Type：Epub+TxT+PDF+Mobi
- Create Date：2021-10-01 09:54:15
- Update Date：2025-09-06
- Status：finish
- Author：Gojko Adzic
- ISBN：0993088112
- Environment：PC/Android/iPhone/iPad/Kindle
- Download
Summary
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。
Reviews
Christoph Kappel
，
This is really quick read， which recaps lots of things that I've read from other books。 For me this is a really good starter and also a nice reference。I especially like the mention of specification by example， but this shouldn't surprise anyone， if you consider Gojko Adzic is one of the authors。 :） This is really quick read， which recaps lots of things that I've read from other books。 For me this is a really good starter and also a nice reference。I especially like the mention of specification by example， but this shouldn't surprise anyone， if you consider Gojko Adzic is one of the authors。 :） 。。。more
Chris Bowley
，
I feel like I gained a fair amount from this book。There's 50 ideas spread out over 4 major parts （Generating Testing Ideas， Designing Good Checks， Improving Testability and Managing Large Test Suites）。 Each idea is covered over 2 pages and includes an introduction， 'Key benefits' and 'How to make it work' sections。 There's also a cartoon drawings to assist each idea。 Whilst this may seem like a gimmick， they can act as visual 'anchors' that assist memory。 The goodThe book is manageable in short I feel like I gained a fair amount from this book。There's 50 ideas spread out over 4 major parts （Generating Testing Ideas， Designing Good Checks， Improving Testability and Managing Large Test Suites）。 Each idea is covered over 2 pages and includes an introduction， 'Key benefits' and 'How to make it work' sections。 There's also a cartoon drawings to assist each idea。 Whilst this may seem like a gimmick， they can act as visual 'anchors' that assist memory。 The goodThe book is manageable in short reading sessions of 10-20minutes which is perfect for staying focused and retaining the information。 It also means it's highly accessible。 In a standard day at work， I now see many test-related aspects in a different light。 Many of the ideas can theoretically be tried out right away。 The format allows the book to more easily act as a reference; when you feel like exercising some of the ideas， you can navigate back to the point of interest within seconds。The not so goodSome ideas are more complicated than others and would've benefitted from more pages with more examples。 Likewise， certain ideas are very simple and could've been detailed in fewer pages。 At times， the contents are almost being held prisoner by the rigid format。 I would've liked a visual number indicator next to each idea to （like the cartoons） assist memory。 When it comes to remembering things， 'more is often more'。 Some of the ideas are fairly obvious to anyone who is aware of the common testing principle of 'put the time in now to save more time later'。 。。。more
Robson Castilho
，
Good advices。 Lacks some more solid examples。 Some topics are very abstract （maybe the author supposes your an experienced QA analyst with background with many tools and practices）。
Kristjan
，
I got more out of this book， than I expected （fifty ideas felt more like 100 ideas）。
Michael McCain
，
Well this is what it says it is。 50 mini articles on various testing techniques。It's not presented in a very digestible format， and lots of the suggestions are implementable only by managers or higher Well this is what it says it is。 50 mini articles on various testing techniques。It's not presented in a very digestible format， and lots of the suggestions are implementable only by managers or higher 。。。more
Peter Dancsok
，
It is an OK book to refresh some base principles。 Nothing exciting nothing new but a good read nevertheless。
Geert
，
expected more。 no aha moments。
Wilson Jimenez
，
Rather than a technical discussion on how to build your tests， the main topic is about how to create your user stories， structure specification through acceptance criteria and leverage team collaboration in order to better test a complete system。Tips are based on real world experiences from the authors， which is good。Authors advocate that tests should focus on value added rather than functional correctness。It's a quick read and description images make it fun。My problems with it are that it feels Rather than a technical discussion on how to build your tests， the main topic is about how to create your user stories， structure specification through acceptance criteria and leverage team collaboration in order to better test a complete system。Tips are based on real world experiences from the authors， which is good。Authors advocate that tests should focus on value added rather than functional correctness。It's a quick read and description images make it fun。My problems with it are that it feels bloated and the title misleading， it seems like a book written for training your manual QA team on how to test-run a system。 From my experience， a dedicated manual QA team in Agile can create problems like a disconnect from development and testing when collaboration is not great between both teams， information loosing due to handoffs， or lack of automated testing from development due to developers delegating all testing tasks to manual testers。 There doesn't seem to be ideas around how to mitigate these type of issues in the book。 。。。more
Gábor László Hajba
，
Not a bad book， it combines ideas from the author's other books like Specification by Example or Fifty Quick Ideas To Improve Your User Stories。The book contains a basic set of ideas which you can apply to your tests， testing strategy， test design if you see them fit。 They are not a must -- and some can be used even in a non-agile project too。What I liked is that you can take some tips and combine it with other resources to see them working。 For example test half-life can be combined with tools Not a bad book， it combines ideas from the author's other books like Specification by Example or Fifty Quick Ideas To Improve Your User Stories。The book contains a basic set of ideas which you can apply to your tests， testing strategy， test design if you see them fit。 They are not a must -- and some can be used even in a non-agile project too。What I liked is that you can take some tips and combine it with other resources to see them working。 For example test half-life can be combined with tools of Adam Tornhill's Your Code as a Crime Scene。 。。。more
Tammy Rhoades-Baldwin
，
I thought this book was very helpful as a business analyst working in agile。 My teammates are reading it now too， and we plan to implement many of these ideas into our testing。
Edward Dahllöf
，
Liked this book better than the user story one， I think the testing topic is too often neglected and this book have some nice ideas that I would like to try out。 I'm not shore about the format， it's repetitive and boring to read in one go， use it rather as a book to flip through。 Liked this book better than the user story one， I think the testing topic is too often neglected and this book have some nice ideas that I would like to try out。 I'm not shore about the format， it's repetitive and boring to read in one go， use it rather as a book to flip through。 。。。more
Christophe Addinquy
，
This book is a kind of follow up on the "Fifty Quick Ideas to Improve your User Stories"。 It's also a follow-up on "Specification by example"。 As such， we'll find excellent complementary adices on acceptance testing。 On the other subject， we may also find some good stuff。 However it doesn't gives anything about the rest of the tests: integration testing， UX， exploratory， performance， etc。 It's probably a well-known choice but for me a bit of frustration。ma note de lecture en français ici This book is a kind of follow up on the "Fifty Quick Ideas to Improve your User Stories"。 It's also a follow-up on "Specification by example"。 As such， we'll find excellent complementary adices on acceptance testing。 On the other subject， we may also find some good stuff。 However it doesn't gives anything about the rest of the tests: integration testing， UX， exploratory， performance， etc。 It's probably a well-known choice but for me a bit of frustration。ma note de lecture en français ici 。。。more
Vuk Trifkovic
，
Excellent book。 It is not an introductory book， rather than help as you go along。 Really want to read the other two books in "50 quick ideas to improve your。。。" series。 Excellent book。 It is not an introductory book， rather than help as you go along。 Really want to read the other two books in "50 quick ideas to improve your。。。" series。 。。。more
Johnny
，
As with the other books of Fifty Quick Ideas you get 50 ideas nicely arranged to a topic。 Most of those ideas are not new and you will have encountered many of them when you wrote your tests。 However， the benefit of this book is that you have them all in one place。 The ideas are often really simple and you can call them common sense。 Until you tried it otherwise you most likely can’t appreciate how helpful those are。 “Describe what， not how”， “Wait for events， not time” or “Minimise UI interacti As with the other books of Fifty Quick Ideas you get 50 ideas nicely arranged to a topic。 Most of those ideas are not new and you will have encountered many of them when you wrote your tests。 However， the benefit of this book is that you have them all in one place。 The ideas are often really simple and you can call them common sense。 Until you tried it otherwise you most likely can’t appreciate how helpful those are。 “Describe what， not how”， “Wait for events， not time” or “Minimise UI interactions” are three simple examples that can cost you hundreds of hours if you don’t follow them。 There is another category of ideas which may easily be overlooked by testers。 Often the problem is not with the technology， but with the people。 Ideas like “Start with always/never” is a great exercise to get examples and test cases from the business users。 Again it’s not rocket science， but it will make your life much easier。 I therefore can only recommend to buy this book and read all ideas， not just the ones you think they help you with the technical side of testing。 。。。more
Sebastian Gebski
，