Luboš's Reviews > Specification by Example

Specification by Example by Gojko Adzic
Rate this book
Clear rating

by
16037775
's review

liked it
bookshelves: software-development

I was about to not finish the book at all because it the introduction was to talkative. But it started be more interesting from the chapter 4. The main message I took is to use behavior-driven development (BDD) e.g. Cucumber but not be focused on tool itself. I would appreciate examples of specification by example, which are not there.
1 like · flag

Sign into Goodreads to see if any of your friends have read Specification by Example.
Sign In »

Quotes Luboš Liked

Gojko Adzic
“Eric Evans argued that agile as a term has lost all meaning because anything can be called agile now.”
Gojko Adzic, Specification by Example

Gojko Adzic
“Like cheap wine, long paper documentation ages rapidly and leaves you with a bad headache if you try to use it a year after it was created. On the other hand, maintaining a system without any documentation also causes headaches.”
Gojko Adzic, Specification by Example

Gojko Adzic
“Beginners think that there is no documentation in agile, which is not true. It’s about choosing the types of documentation that are useful.”
Gojko Adzic, Specification by Example

Gojko Adzic
“Adam Geras puts this more eloquently: “Quality is about being prepared for the usual so you have time to tackle the unusual.”
Gojko Adzic, Specification by Example

Gojko Adzic
“Implementing functional test automation will get the team to work closer and prepare the system for the use of executable specifications later.”
Gojko Adzic, Specification by Example

Gojko Adzic
“Sell Specification by Example as a better way to do acceptance testing”
Gojko Adzic, Specification by Example

Gojko Adzic
“Watch out for people who implement more than what was agreed on and specified with examples”
Gojko Adzic, Specification by Example

Gojko Adzic
“The F-16 was successful because the design provided a better and cheaper solution than what the customer asked for.”
Gojko Adzic, Specification by Example

Gojko Adzic
“As the data is shared, tests influence each other. People get confused very quickly. This is a premature optimization. Write tests to be data agnostic.”
Gojko Adzic, Specification by Example

Gojko Adzic
“Find the most annoying thing, fix it, and repeat”
Gojko Adzic, Specification by Example


Reading Progress

February 25, 2016 – Shelved
February 25, 2016 – Shelved as: to-read
February 25, 2016 – Shelved as: software-development
August 30, 2016 – Started Reading
September 7, 2016 – Finished Reading

No comments have been added yet.