Another Look at WatiN
At my current client, we’ve decided to use WatiN, largely for the C# vs. Ruby reason I discussed earlier this week. After spending a week working with WatiN (following a year of rarely using it), I’m...
View ArticleWatiN Patterns #1: No Browser Left Behind
In my previous posts on WatiN, I lamented the shortage of online documentation and resolved to do something about it by documenting the patterns I’ve found for good WatiN tests. This is the first in a...
View ArticleWatiN Patterns #2: One Assertion and a Name to Match
One way to keep your WatiN tests maintainable is to keep them small and focused. WatiN Pattern #2, then, is a way to do just that. Your tests should assert one thing. Just one. And the name of the test...
View ArticleClik here to view.
Patterns for Splitting User Stories
Good user stories follow Bill Wake’s INVEST model. They’re Independent, Negotiable, Valuable, Estimable, Small, and Testable. The small requirement drives us to split large stories. But the stories...
View ArticleWatiN Patterns #3: Don’t Over-specify
After a long hiatus, I’m resuming the WatiN Patterns series. Pattern #1 covered why and how your tests should clean up after themselves. Pattern #2 covered how you should name your tests and why they...
View ArticleAnother Story Splitting Pattern (Maybe)
User stories are typically written using a template like, “As a <role>, I want to <action> so that <value>.” My other story splitting patterns focus on complexity in the action part...
View Article