Copyright
Brief Table of Contents
Table of Contents
Foreword
Preface
Acknowledgments
About this Book
About the Cover
Chapter 1. Introduction to specification by example and Gherkin
1.1. What’s a specification?
1.2. Why do teams need specifications?
1.2.1. Defining acceptance criteria in specifications
1.2.2. Building a ubiquitous language into specifications
1.3. Common specification pitfalls
1.3.1. Over-specification
1.3.2. Hand-offs
1.3.3. Under-documentation
1.3.4. Speci-fiction
1.3.5. Test-inability
1.4. Meet specification by example and Gherkin
1.4.1. Key process patterns
1.5. Having conversations that identify business needs
1.5.1. Deriving scope from goals
1.5.2. Illustrating requirements with examples
1.5.3. Specifying collaboratively
1.6. Long-term benefits of automating conversations
1.6.1. Automating tests based on examples
1.6.2. Validating frequently
1.6.3. Living documentation
1.7. Capturing conversations as executable specifications
1.8. Making software that matters
1.9. Summary
1. Writing executable specifications with examples
2.2.1. Feature