Re: Debugging Test Execution
Rick Mugridge <[email protected]> Thu, 25 Sep 2003 16:40:07 +1200
| Newsgroups | gmane.comp.programming.tools.fit.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============35027796301652647== Content-Type: multipart/alternative; boundary="------------000709010908020604070806" This is a multi-part message in MIME format. --------------000709010908020604070806 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit There's an easy way to get the html in order to run Fit while you're debugging. Grab the html that fitnesse produces to the browser and chop out the page-level table that encloses the fit tables inside. Rick [email protected] wrote: >----- Original Message ----- >From: "Stefan Roock" <[email protected]> >To: "FIT Developers" <[email protected]> >Sent: Wednesday, September 24, 2003 1:50 PM >Subject: [Fit-dev] Debugging Test Execution > > > > >>Hi, >>when an acceptance test fails, it is sometimes difficult to determine >>the exact reason. Then it would be nice to be able to debug the test >>execution. >> >>It that possible with fitnesse? >> >> > >Fitnesse simply executes FIT in a separate process, and collects >the HTML output via a pipe. If I actually needed to do a debugging >session (which is what I think you're asking about) I'd run FIT in >the development environment and ignore FitNesse. > >John Roth > > > > > >>Stefan >>-- >> >> > > >_______________________________________________ >Fit-dev mailing list >[email protected] >http://lists.freepan.org/mailman/listinfo.cgi/fit-dev > > --------------000709010908020604070806 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body text="#000000" bgcolor="#ffffff"> There's an easy way to get the html in order to run Fit while you're debugging. Grab the html that fitnesse produces to the browser and chop out the page-level table that encloses the fit tables inside.<br> <br> Rick<br> <br> <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> wrote:<br> <blockquote type="cite" cite="[email protected]"> <pre wrap="">----- Original Message ----- From: "Stefan Roock" <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a> To: "FIT Developers" <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a> Sent: Wednesday, September 24, 2003 1:50 PM Subject: [Fit-dev] Debugging Test Execution </pre> <blockquote type="cite"> <pre wrap="">Hi, when an acceptance test fails, it is sometimes difficult to determine the exact reason. Then it would be nice to be able to debug the test execution. It that possible with fitnesse? </pre> </blockquote> <pre wrap=""><!----> Fitnesse simply executes FIT in a separate process, and collects the HTML output via a pipe. If I actually needed to do a debugging session (which is what I think you're asking about) I'd run FIT in the development environment and ignore FitNesse. John Roth </pre> <blockquote type="cite"> <pre wrap="">Stefan -- </pre> </blockquote> <pre wrap=""><!----> _______________________________________________ Fit-dev mailing list <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> <a class="moz-txt-link-freetext" href="http://lists.freepan.org/mailman/listinfo.cgi/fit-dev">http://lists.freepan.org/mailman/listinfo.cgi/fit-dev</a> </pre> </blockquote> </body> </html> --------------000709010908020604070806-- --===============35027796301652647== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Fit-dev mailing list [email protected] http://lists.freepan.org/mailman/listinfo.cgi/fit-dev --===============35027796301652647==--