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.
Pages
Follow me on Twitter!
My Tweets-
Recent Posts
Recent Comments
- 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
Categories
- bdd
- breaking models
- business value
- capability red
- coaching
- complexity
- conference
- csharp
- cynefin
- deliberate discovery
- evil hat
- feedback
- humour
- jbehave
- kanban
- lean
- learning
- learning models
- life
- nlp
- open source
- real options
- scale
- scrum
- spike and stabilize
- stakeholders
- stories
- testing
- Uncategorized
- uncertainty
- values
- writing
Archives
Meta
Your link is broken. It should be: http://www.testingreflections.com/node/view/7585
Fixed, thanks Nate!