Sponsored By Aspose - File Format APIs for .NET

Aspose are the market leader of .NET APIs for file business formats – natively work with DOCX, XLSX, PPT, PDF, MSG, MPP, images formats and many more!

StoryTeller on InfoQ

InfoQ just put up an interview with me talking about StoryTeller.  I *will* get more information up about StoryTeller soon.  The next post is going to be about doing table driven testing.

About Jeremy Miller

Jeremy is the Chief Software Architect at Dovetail Software, the coolest ISV in Austin. Jeremy began his IT career writing "Shadow IT" applications to automate his engineering documentation, then wandered into software development because it looked like more fun. Jeremy is the author of the open source StructureMap tool for Dependency Injection with .Net, StoryTeller for supercharged acceptance testing in .Net, and one of the principal developers behind FubuMVC. Jeremy's thoughts on all things software can be found at The Shade Tree Developer at http://codebetter.com/jeremymiller.
This entry was posted in StoryTeller. Bookmark the permalink. Follow any comments here with the RSS feed for this post.
  • http://codebetter.com/members/jmiller/default.aspx Jeremy D. Miller

    @Toddb,

    I can’t say that I’m thrilled about the [FormatAs()] business, but I most definitely did not want the old FIT DoFixture syntax problem, so it stays. At least the FormatAs gives you the ability to fine tune the test language without breaking the test.

    Refactoring? Sigh, I think it’s perfectly possible, but that’s for next spring.

  • toddb

    I’ve just been looking at your source code and running the samples. I like what I see. At first I wondered about your use of the FormatAs attribute and whether you should have just done reflection on the method name but can see that it works well and sets up a cleaner convention. Simple and effective – I am a co-author on StoryQ and think I’ll take this idea into that library.

    I think that you’ve nailed two of my problems with fitnesse – version control and a GUI for testers/analysts/business. (I don’t have to have it distributed.)

    Question: how are you planning to deal with refactoring? This seems to me a key problem when the test bases get large. This is something that Rick Mugridge has been looking at with ZiBreve.

    I’m looking forward to more.

  • http://codebetter.com/members/jmiller/default.aspx Jeremy D. Miller
  • http://blogger.forgottenskies.com Steve

    Great to hear.

    Can I suggest a simple ‘how to get started’ blog post before you get too into the nitty gritty blog posts? :)

    Thanks – and I look forward to using StoryTeller