Antony Marcano’s written a great post on testing for exceptions in a way which makes the example much easier to read, and keeps the Given / When / Then flow intact. I like this very much, and will be doing it this way from now on (aversion to defensive programming notwithstanding).
- All posts are released under CC 3.0 by-sa unless otherwise stated.
Follow me on Twitter!My Tweets
- Guillermo Chussir on There’s no such thing as Declarative and Imperative
- Originate Guides - Storywriting Best Practices - Originate | Concept-to-launch Acceleration Partner for Digital Products & Experiences on Feature Injection and handling technical stories
- Agile Requirements & Behavior Driven Development | Pragmatic Coders on Estimating Complexity
- breaking models
- business value
- capability red
- deliberate discovery
- evil hat
- learning models
- open source
- real options
- spike and stabilize