Lean-agile acceptance test driven development : better software through collaboration
In Acceptance Test Driven Development (ATDD), developers work with customers and testers to create acceptance tests that thoroughly describe how software should work from the customer’s viewpoint. By tightening the links between customers and agile teams, ATDD can significantly improve both software...
| Otros Autores: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
[Place of publication not identified]
Addison Wesley Professional
2011
|
| Edición: | 1st edition |
| Colección: | Net objectives lean-agile series Lean-agile acceptance test-driven development
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009629152106719 |
Tabla de Contenidos:
- Cover
- Contents
- Introduction
- Part I: The Tale
- Chapter 1: Prologue
- Ways to Develop Software
- The Importance of Acceptance Tests
- System and Team Introduction
- Summary
- Chapter 2: Lean and Agile
- The Triad and Its Units
- Post-Implementation Tests
- Quick Feedback Better Than Slow Feedback
- Preimplementation Tests
- Lean and Agile Principles
- Summary
- Chapter 3: Testing Strategy
- Types of Tests
- Where Tests Run
- Test Facets
- Summary
- Chapter 4: An Introductory Acceptance Test
- A Sample Business Rule
- Implementing the Acceptance Tests
- Testing Process
- Summary
- Chapter 5: The Example Project
- The Charter
- High-Level Requirements
- Summary
- Chapter 6: The User Story Technique
- Stories
- INVEST Criteria
- Summary
- Chapter 7: Collaborating on Scenarios
- Use Cases from User Stories
- Story Map
- Conceptual Flow
- Communication
- Summary
- Chapter 8: Test Anatomy
- Triad Creates Tests
- Test Context
- Test Structure
- Tests with Example Values
- Test with Values in Text
- When and Where Tests Are Run
- Summary
- Chapter 9: Scenario Tests
- Tests for Exception Scenarios
- Tests for Business Rules
- Cross-Story Issues
- Don't Automate Everything
- Multi-Level Tests
- User Interface Tests
- Check the Objectives
- Summary
- Chapter 10: User Story Breakup
- Acceptance Tests Help Break Up Stories
- Business Rule Tests
- A Story with a Business Rule
- Summary
- Chapter 11: System Boundary
- External Interfaces
- External Interface Tests
- What Is Real?
- Story Map of Activities
- Summary
- Chapter 12: Development Review
- The Rest of the Story
- Deployment Plans
- From Charter to Deliverable
- Summary
- Part II: Details
- Chapter 13: Simplification by Separation
- Complex Business Rules
- Rental History
- Summary
- Chapter 14: Separate View from Model.
- Decouple the User Interface
- Decoupling Simplifies Testing
- Summary
- Chapter 15: Events, Responses, and States
- Events and an Event Table
- States and State Transitions
- Internal State or External Response
- Summary
- Chapter 16: Developer Acceptance Tests
- Component Acceptance Tests
- Summary
- Chapter 17: Decouple with Interfaces
- Tests for a Service Provider
- Separating User Interface from Service
- Reusable Business Rules
- Summary
- Chapter 18: Entities and Relationships
- Relationships
- Summary
- Chapter 19: Triads for Large Systems
- Large Systems
- When a Customer Test May Not Be Required
- What If There Are No Tests?
- Summary
- Part III: General Issues
- Chapter 20: Business Capabilities, Rules, and Value
- Business Capabilities
- Scenario Handling
- Business Rules Exposed
- A Different Business Value
- Summary
- Chapter 21: Test Presentation
- Customer Understood Tables
- Table Versus Text
- Specifying Multiple Actions
- Complex Data
- Custom Table Forms
- Summary
- Chapter 22: Test Evaluation
- Test Facets
- Test Sequence
- Test Conditions
- No Implementation Issues
- Points to Remember
- Summary
- Chapter 23: Using Tests for Other Things
- Uses of Acceptance Tests
- Tests as a Bug Report
- Summary
- Chapter 24: Context and Domain Language
- Ubiquitous Language
- Two Domains
- Summary
- Chapter 25: Retrospective and Perspective
- Recap
- What's the Block?
- Benefits
- Summary
- Part IV: Case Studies
- Chapter 26: Case Study: Retirement Contributions
- Context
- The Main Course Test
- Business Value Tracking
- One Exception
- Another Exception
- Two Simultaneous Exceptions
- The Big Picture
- Event Table
- State Transition Table
- Summary
- Chapter 27: Case Study: Signal Processing
- It's Too Loud
- Sound Levels
- Developer Tests
- Summary.
- Chapter 28: Case Study: A Library Print Server
- The Context
- A Workflow Test
- Summary
- Chapter 29: Case Study: Highly Available Platform
- Context for Switching Servers
- Test for Switching Servers
- Test for Technical Rule
- Summary
- Part V: Technical Topics
- Chapter 30: How Does What You Do Fit with ATDD?
- Test Platforms
- Internal Design from Tests
- Device Testing
- Starting with User Interfaces
- Black Box Testing
- Unit Testing
- Summary
- Chapter 31: Test Setup
- A Common Setup
- Some Amelioration
- Test Order
- Persistent Storage Issues
- Summary
- Chapter 32: Case Study: E-Mail Addresses
- Context
- Breaking Down Tests
- Summary
- Part VI : Appendices
- Appendix A: Other Issues
- Context
- Customer Examples
- Requirements and Acceptance Tests
- Testing Systems with Random Events
- The Power of Three
- Summary
- Appendix B: Estimating Business Value
- Business Value
- Developer Stories
- Summary
- Appendix C: Test Framework Examples
- The Examples
- Fit Implementation
- Slim-Table Style
- Slim-Cucumber Style
- Robot
- Cucumber
- Test Frameworks
- Summary
- Appendix D: Tables Everywhere
- User Interface Tests with Tables
- Requirement Tables
- Quality Attribute Requirements
- Data Tables
- Summary
- Appendix E: Money with ATDD
- The Context
- The Original Tests
- The Acceptance Test Approach
- Summary
- Appendix F: Exercises
- Calculator
- More Exercises
- References
- Epilogue
- Index.
