« Table of Contents »
Previous Chapter « The Behaviour Specification Writing Process
The Behaviour Specification Handbook
General Tips
This chapter in The Behaviour Specification Handbook provides general tips for writing effective Behaviour Specifications.
- The Software Component Context Is King
- Avoid Specifying Internal Technical Implementation Details
- Specify Relevant Business Capabilities
- Specify Component Interaction Behaviours
- Write One Specification For One Behaviour
- Use Present Tense
- Avoid Generic Verbs
- Write In Everyday Business Language
- SpecFlow/Cucumber Is Only The Name Of A Tool
- Have Different Feature Files For Different User Interfaces
Next » Software Component Context Is King
Next Chapter » Effective Behaviour Specification Descriptions