Thanks for the suggestions Aslak. I ended up doing pretty much what you said. I added a custom formatter that added a little functionality onto the HTML formatter. Instead of using a server all I did was use prototype/lowpro to refresh the page until all the specs were complete. I then used an autotest hook to have the browser refresh using applescript. Except for the last part it is all works on any machine with a browser.
I have some ideas of how to work in the story runner in my tool... I know you were working on the HTML docs/ little app for plain text stories. Have you make any progress since your blog post about it? Thanks, Ben aslak hellesoy wrote: > On Nov 11, 2007 4:33 PM, Ben Mabey <[EMAIL PROTECTED]> wrote: > >> I was thinking that a little window(cocoa) or maybe just a browser >> window could display the summary of the test run like autotest does and >> then the failed specs in HTML format. Not the entire HTML report would >> be generated/displayed- only the failing ones would be so it would be >> manageable on projects with large test suites. So, instead of having a >> terminal window open with autotest it would just be a stand alone window. >> >> > > I think the simplest and best thing here would be a pure browser > solution with autorefresh. > It should only be a matter of tweaking the HTML output a little to: > * Implement autorefresh. Ajax based would require a lite server > (webrick). Or just META refresh would work on the file system. > * Tweak the HTML output to only output the red specs, not the green ones. > > I don't like the cocoa idea - too proprietary. The qlmanage wouldn't > provide much value beyond growl bubbles. You wanted to click on the > HTML and go to the editor right? > > Aslak > > >> aslak hellesoy wrote: >> >>> Where would the HTML report be displayed? >>> >>> On Nov 11, 2007 6:38 AM, Ben Mabey <[EMAIL PROTECTED]> wrote: >>> >>> >>>> Hey all, >>>> I was just wondering if any one has played around with getting >>>> autotest's rspec integration working with rspec's HTML output. I really >>>> like how in the rspec textmate bundle the context of the failing code >>>> is inlined with the failing spec along with the exact line highlighted >>>> and a link to the exact spot in reference. However, I rarely use this >>>> nice output since autotest is so convenient... So, I was thinking >>>> wouldn't it be great to have the best of both worlds? What do you >>>> think? And before I try and do this, has anyone else already done it? >>>> >>>> >>>> -Ben >>>> >>>> >>>> _______________________________________________ >>>> rspec-users mailing list >>>> rspec-users@rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/rspec-users >>>> >>>> >>>> >>> _______________________________________________ >>> rspec-users mailing list >>> rspec-users@rubyforge.org >>> http://rubyforge.org/mailman/listinfo/rspec-users >>> >>> >> _______________________________________________ >> rspec-users mailing list >> rspec-users@rubyforge.org >> http://rubyforge.org/mailman/listinfo/rspec-users >> >> > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users > _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
