RE: chunked output
"Charlie Poole" <[email protected]> Mon, 18 Aug 2003 17:05:01 -0700
| Newsgroups | gmane.comp.programming.tools.fit.devel |
|---|---|
| Message-ID | <[email protected]> |
Micah asked: > It can take a long time to run some tests. > > I worked with one team that used FitNesse to test thier web app. Simple > tests ran in 10 secs but some of the longer ones took up to 2 minutes. To > run a suite of tests...whew... come back after lunch! > > The problem with these tests is that you don't get any feedback until > execution has completely finished. You click the button and you have no > idea what is going on until you get ALL the results. It would be really > nice if you could see each table turn green or red as soon as it was > processed. The entire test might take a few minutes to finish > but you would > see progress as it was made. > > By using chunked encoding I can make FitNesse do this. But it means that > FIT will need to spit out the results as soon as it makes them. FIT needs > chunked output. > > Now for the purpose of web pages it doesn't make sense to output anything > less than table. Browsers cannot format a table untill they have > the ending > </table> tag. So if FIT could output a table at a time, that > would make me > happy. > > Please consider this feature for 1.0 So is 1.0 supposed to consolidate and codify or add new features or a little of each? Charlie Poole [email protected] www.pooleconsulting.com www.charliepoole.org