aspose file tools*
The moose likes Agile and Other Processes and the fly likes Fitnesse Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Fitnesse" Watch "Fitnesse" New topic
Author

Fitnesse

Unnsse Khan
Ranch Hand

Joined: Nov 12, 2001
Posts: 511
Hello there,

I read the the tutorial for Fitnesse and was very impressed!

Question(s):

(1) Where is the JavaDoc API (web docs) for FIT?

(2) Is there an Eclipse plug-in for Fitnesse (and if there is, what
does it do)?

(3) Any good online tutorials or books? The tutorial that comes
bundled with Fitnesse doesn't really explain how to write the
intermediary code which binds fixtures (written in Java) with FIT
tables (located in the wiki). Would appreciate it if some one could
point me to a good URL or book which explains everything.

(4) Is it plausible to use Fitnesse to write user acceptance tests /
customer tests for web applications which are connected to a Hibernate
ORM based persistence layer?

Sincerely yours,
[ March 14, 2007: Message edited by: Unnsse Khan ]
Stan James
(instanceof Sidekick)
Ranch Hand

Joined: Jan 29, 2003
Posts: 8791
I really don't remember where I got enough doc to integrate Fit with my own Wiki but it wasn't terribly hard. Maybe the FitDocumentation page. See also the Fit Book online or the Fit Book dead trees.

I'll skip to #4 ... I worked on a system where almost nothing was testable without having the EJB server up and running. I thought about running Fit tests inside there and never got that far. If you have things you can JUnit test outside your server, you can proabably Fit test them, too.

Someone may open the debate of "it isn't x kind of test if it uses the database" but I really don't care as long as it's convenient and fast enough to run often.

All Java testing aside, I wanted to use Fit to specify and test database data. We had a great many rules that were data driven. I trusted the code, but not the data migration. I made a generic fixture that tested "For a given SQL query (of any complexity you like) you should get these results." The folks who really did the work were not sold; they insisted on Use Case Documents and Mercury tests of the UI, both of which were pretty evil.

Best of luck with Fitnesse. I think it's a great way to go!
[ March 14, 2007: Message edited by: Stan James ]

A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Fitnesse