History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: WET-355
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Alister Scott
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
WET

Optional Integration of FitNesse into WET

Created: 24/May/07 01:14 AM   Updated: 29/Jun/07 04:44 PM
Component/s: None
Affects Version/s: 0.8.0, 1.0.0, 0.9.8_beta1, 0.9.8 Final, 0.9.8_Patch
Fix Version/s: 1.2

Original Estimate: 2016h Remaining Estimate: 2016h Time Spent: Unknown


 Description  « Hide
I was thinking it would be nice to optionally integrate FitNesse into WET in the future.
FitNesse (http://fitnesse.org/) is an open acceptance testing framework that is driven by wiki pages and tables within.
The benefit is tests can be executed directly from FitNesse and it produces summaries of results based upon assertions.
FitNesse also has an API so that tests can be executed in 'batch', or be scheduled to run.
The limitation of FitNesse (I believe) is it doesn't have a good way of displaying a history of results.
I think there has already been some effort getting watir to work in FitNesse called 'Faucets' (http://faucets.rubyforge.org/)

Please feel free to comment on this issue whether this is a good/bad idea, and whether it is something that would suit the vision of WET.

 All   Comments   Work Log   Change History      Sort Order:
Raghu Venkataramana - 26/May/07 06:57 AM
+1. This does feel like a nice to have feature.

Raghu Venkataramana - 18/Jun/07 10:27 AM
This is an issue that I believe should be addressed in 1.2. I would encourage folks to pitch in some ideas here.

bill ryder - 19/Jun/07 10:01 AM
I like the idea! I have been using WET for about a year now and was just looking into how to connect FIT, FitNesse, (RubyFIT & Faucets) into WET. A successful integration of FitNesse into WET would be a 'powerful' improvement of testing scope and consistent with spirit of WET; in particular the enhanced ability to address acceptance testing as an aspect of requirements discovery (agile) and pre-implementation from the testers view.

Alister Scott - 29/Jun/07 04:44 PM
Comment from Sai Hawk via email:

"Its an extremely good idea. I have already writen tests with fitnesse using WATIN. Fitnesse is particularly suitable because you have a way of clearly expressing your tests as tables which act as concrete examples. As well I extensively use Do Fixture which helps me to write business facing tests very easily.
 
Regards,
Sai"