Ticket #2425 (closed task: wontfix)
Opened 6 years ago
Last modified 6 years ago
Integrate Trac With FitLibrary
| Reported by: | PeterMerel | Owned by: | jonas |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | ticket system | Version: | 0.9 |
| Severity: | normal | Keywords: | |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
Fitnesse (http://fitnesse.org) is a popular but proprietary, crufty, and generally get-in-your-way wiki wrapper around Cunningham's spectacularly brilliant FitLibrary (http://www.cs.auckland.ac.nz/~rick/FitLibrary/).
Fitnesse as a project is for all intents dead, but it has a large user community who are generally dealing with PM tasks on a day to day basis. An integration of Trac with FitLibrary would be enormously popular among existing Fitnesse users, and would capture critical mindshare among testers and PMs in general.
The way to do this is simply to render Trac's existing table format as html and stuff it into the FitLibrary for testing and consequent colouring. The goodness deriving from attaching these tests to tickets as well as wiki pages, to track acceptance test from requirement to working acceptance, and for testers to attach new non-working tests to bug-tickets, would be HUGE'. And the implementation cost is tiny.
FitServer's exist for C#, Java, and Python. Test tickets should have a property enabling tests to be directed to a particular FitServer, and there should be a settable default for this naturally.
Attachments
Change History
comment:1 Changed 6 years ago by anonymous
comment:3 Changed 6 years ago by cmlenz
- Resolution set to wontfix
- Status changed from new to closed
It'd be nice if Trac Tickets could integrate with Selenium too. Not exactly the same level of testing ... but FIT tests on frameworks that map method calls to URL arguments could easily be adapted this way ...