• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Fit testing framework

 
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Is anyone out there into the Fit Testing Framework? I looked at it a while ago and was overwhelmed by the fixtures. But today I downloaded some code and looked into it further and it's pretty cool. I was able to integrate it into my own Wiki with this much code:

Wondered if anybody was using fit or Fitnesse (currently down?) and could share advice about building fixtures. Thanks!
[ November 17, 2003: Message edited by: Stan James ]
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have played a little bit with FitNesse - see http://bloodball.sf.net/
What do you want to discuss?
 
Stan James
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Have you built any multi-phase tests like the Music examples on fit.c2.com? They left the results of one fixture in a public static var and used it in the next fixture, which seemed a little tacky. We could at least use ThreadLocal to avoid collisions between users.
In much the same style, I'm thinking about a first fixture that can do a variety of database queries (all yielding a common set of columns) and a second one that will assert various things about the resultset. Does that sound reasonable?
 
Ilja Preuss
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Stan James:
Have you built any multi-phase tests like the Music examples on fit.c2.com? They left the results of one fixture in a public static var and used it in the next fixture, which seemed a little tacky. We could at least use ThreadLocal to avoid collisions between users.


Yes - I think all my tests look like that - see TestAbortTackle for an example.
You are right that using a static variable feels wrong - there is some discussion of the topic at the fit-dev list under the subject "saving state between fixtures".

In much the same style, I'm thinking about a first fixture that can do a variety of database queries (all yielding a common set of columns) and a second one that will assert various things about the resultset. Does that sound reasonable?


Yes, it does. It's a common pattern, currently known under a bunch of names - for example Build Operate Check
reply
    Bookmark Topic Watch Topic
  • New Topic