My wife and son are going away for two weeks soon to visit family in Texas. I’m seizing the opportunity to
fire up ye olde XBox finally wrap up StoryTeller 1.0 (basically a tool for maximizing the usefulness of Fit testing and a .Net centric replacement for FitNesse). As a runup to the first real StoryTeller release, and to continue the thread on Fit/FitNesse testing and executable requirements that’s been going around, I’m going to spit out some little posts (plus one big post) all week on tips and tricks for Fit testing and some lessons I’ve learned on automating acceptance tests. I haven’t used every possible tool out there, but I’ve done a lot of test automation with a mixed bag of results. Check in occasionally and I might accidentally post something to help out some test automation newbies.
- Fail Fast
- Dependency Injection trickery
- Extending FitnesseDotNet with custom type handlers
- Don’t Repeat Yourself
- Jumping back into “Build a CAB” to do the Subcutaneous Testing chapter because Ian Cooper keeps mentioning it and a client developer and I are plotting a way to do just that in his code next week.
- Maybe try one more stab at creating a DSL with FitnesseDotNet’s DoFixture and comparing that to either a Fluent Interface in C# and/or a Ruby equivalent. That might take a bit of effort, but I’m dying to see how the three choices with “feel”
Anyway, the first one will hit tonight.