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
Where would the HTML report be displayed?
On Nov 11, 2007, at 12:29 pm, aslak hellesoy wrote:
Where would the HTML report be displayed?
The Quick Look feature in Leopard can be controlled from the command
line using qlmanage, if that is worth looking into. Obviously, no
good to non-Mac users though
Ashley
–
blog @ http://aviewfromafar.net/
linked-in @ http://www.linkedin.com/in/ashleymoran
currently @ home
Ashley M. wrote:
Ashley
Thanks for the tip Ashley! I’ll look into it!
-Bne
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.
On Nov 11, 2007 4:33 PM, Ben M. [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
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
I’ve always secretly thought that Adobe Air might be a good candidate
for
something like this, I just never got around to actually trying to do
something about it.
Air runs on Windows/Linux/OSX, can render HTML just fine, and can
interact
with the local filesystem to an extent. Last time I checked it’s not
able
to run any commands on the target system, so you can’t have it trigger
tests… but if Autotest was running and writing results to a file, you
should be able to rig something together.
Don
On Sun, 2007-11-11 at 17:21 +0100, aslak hellesoy wrote:
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.
I’ve been using this approach on and off for a while, using the META
refresh technique both off of the file system and through a web server.
I don’t right now because it was taking up a bit too much screen space.
Now that I’ve got a second monitor to hook up that may change again.
I’ve been using a refresh rate of 30s, but that’s actually already too
slow. I guess a better solution would be to be able to trigger an action
after specs have run. The actual command could just be a shell command
defined in the spec.opts file, so that people can do whatever is the
right thing for their platform and environment.
- Tweak the HTML output to only output the red specs, not the green ones.
That would be useful.
Kind regards,
Hans