You are trying to test a lot of things at the same time, which is one of
the reasons that it is now hard to diagnose a problem.
I would tackle this by
a) writing a separate spec for the partial _question_for_candidate
b) write a separate spec for the helper that renders the question
b) in the
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
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 @
On Nov 10, 2007 11:12 AM, aslak hellesoy [EMAIL PROTECTED] wrote:
be_success has the same semantics (and uses) Response#success? and
that's not our API, but Rails'
If you don't like Rails' semantics you can make your own matcher, but
I don't want to invent a whole new API on top of Rails in
Ashley Moran wrote:
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
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
Slowly digging to the bottom of this one.
If I add
Test::Unit::TestCase.fixture_path = RAILS_ROOT + '/spec/fixtures/'
to my spec_helper.rb, then everything runs fine. So presumably there
is somewhere that config.fixture_path from the Spec::Runner.configure
block is supposed to get put into
On Nov 08, 2007, at 6:07 pm, Alvin Schur wrote:
My goal is to detect inter-dependencies sooner than later...
I have to say I've NEVER run specs backwards. Am I sitting on a time
bomb? Are there subtle traps that can create inter-dependencies
between specs? To look at my
On Nov 11, 2007 11:01 AM, Alvin Schur [EMAIL PROTECTED] wrote:
On Nov 08, 2007, at 6:07 pm, Alvin Schur wrote:
My goal is to detect inter-dependencies sooner than later...
I have to say I've NEVER run specs backwards. Am I sitting on a time
bomb? Are there subtle traps that
On Nov 11, 2007 8:29 AM, Leslie Freeman [EMAIL PROTECTED] wrote:
Slowly digging to the bottom of this one.
If I add
Test::Unit::TestCase.fixture_path = RAILS_ROOT + '/spec/fixtures/'
to my spec_helper.rb, then everything runs fine. So presumably there
is somewhere that config.fixture_path
On Nov 11, 2007, at 12:47 PM, David Chelimsky wrote:
On Nov 11, 2007 11:01 AM, Alvin Schur [EMAIL PROTECTED] wrote:
On Nov 08, 2007, at 6:07 pm, Alvin Schur wrote:
My goal is to detect inter-dependencies sooner than later...
I have to say I've NEVER run specs backwards. Am I sitting
On Nov 11, 2007 3:50 PM, Scott Taylor [EMAIL PROTECTED] wrote:
On Nov 11, 2007, at 12:47 PM, David Chelimsky wrote:
On Nov 11, 2007 11:01 AM, Alvin Schur [EMAIL PROTECTED] wrote:
On Nov 08, 2007, at 6:07 pm, Alvin Schur wrote:
My goal is to detect inter-dependencies sooner than
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
On Nov 12, 2007 12:45 AM, s.ross [EMAIL PROTECTED] wrote:
does this mean that:
rake spec:doc
will not produce plain text specdocs?
No, spec:doc will remain untouched.
I'm not talking about --format specdoc (which the spec:doc task uses),
but --format rdoc, which is supposed to create RDoc
On Nov 11, 2007 8:39 PM, aslak hellesoy [EMAIL PROTECTED] wrote:
I'm doing some housekeeping and just realised that the rdoc formatter
produces gibberish:
http://rspec.rubyforge.org/rdoc/files/EXAMPLES_rd.html
Will anyone protest if I just go ahead and remove it? (I can't imagine
anyone
On Nov 11, 2007 12:36 PM, Brian Takita [EMAIL PROTECTED] wrote:
On Nov 11, 2007 8:29 AM, Leslie Freeman [EMAIL PROTECTED] wrote:
Slowly digging to the bottom of this one.
If I add
Test::Unit::TestCase.fixture_path = RAILS_ROOT + '/spec/fixtures/'
to my spec_helper.rb, then
Hi Hans,
I rewrote my specs the way you suggested and now everything works!
For those who are interested, here's how the code looks like now (after
following Hans' tips).
a) writing a separate spec for the partial _question_for_candidate
require File.dirname(__FILE__) + '/../../spec_helper'
17 matches
Mail list logo
