[理学]验收测试驱动开发实战.ppt

验收测试驱动开发实战 Acceptance Test Driven Development in practice Steven Mak 麥天志 steven@ What are we up to now? Lost in translation Do not explain why Gaps discovered only until coding started Cumulative effects of small misunderstandings Inadequate and essentially flawed requirements and specifications Failing to meet actual needs are obvious things really obvious? Fulfilling specifications does not guarantee success Imperative requirements Meeting the needs with Acceptance TDD Drive implementation of a requirement through a set of automated, executable acceptance tests ATDD in a Nutshell Real-world examples to build a shared understanding of the domain Select a set of these examples to be a specification and an acceptance test suite Automate the verification of acceptance tests Focus the software development effort on the acceptance tests Use the set of acceptance tests to facilitate discussion about future change requests. The ATDD cycle Benefits of ATDD Comprehensible examples over complex formulas Close Collaboration Definition of Done Co-operative Work Trust and Commitment Testing on system level Variations - an escape? Behaviour-driven development Example-driven development Executable specifications Names do not matter, but underlying practices matter Worthwhile to try if your business people do not like “testing” Ideal candidate to work with Shared interest in success Authority to make decision Ability to understand implications Ability to explain the domain Specification by Examples Use realistic examples to demonstrate differences in possibilities instead of abstract requirements Write specifications down as tables Workflows: Preconditions Processing steps Verifications Examples, Tests, and Spec Specification workshop Ask the domain experts Developers and testers should suggest examples of edges or important issues for discussion Ubiquitous language Organise feedback to ensure shared understanding Use facilitator to stay focused if needed Acceptance criteria Wri