Hello,
In addition, I get some other errors and couldn't get the spec run. So
finally I found that it was a compatibility issue of RSpec_1.0.8 and I
have to use trunck for Rspec and Rspec_on_rails instead using plugin.
http://www.ruby-forum.com/topic/129741
link to it,
http://rspec.rubyforge.
I just read David Chelimsky's slides from RailsConf. I was at
RailsConf, but was unable to attend the session. The slides are
excellent, and I've recently become VERY interested in stories. In
particular I'm a bit unhappy with regular view testing (even with the
easier notion of it in RSpec). I
>> I just got back from RailsConf, and upgraded on of my development apps to
>> 2.1, and now autotest is going into an infinite loop. It runs tests
>> continuously instead of waiting for files to be saved before rerunning.
>>
>> Has anybody else seen this, or know how to get around it?
I had this
On Thu, Jun 19, 2008 at 9:41 AM, Jim Lindley <[EMAIL PROTECTED]> wrote:
>>> I just got back from RailsConf, and upgraded on of my development apps to
>>> 2.1, and now autotest is going into an infinite loop. It runs tests
>>> continuously instead of waiting for files to be saved before rerunning.
>
On Thu, Jun 19, 2008 at 9:31 AM, Christopher Bailey
<[EMAIL PROTECTED]> wrote:
> Specifically, I'm wondering, or contemplating, if I do unit tests for
> my models, and then I use WebRat plus RailsStory, do I even need to
> then do functional testing of my controllers and views? I can see
> that I
Kyle, thanks much for sharing your experience. You mention the speed
and so on. I've read that it is slow. Question: does Autotest work
the same way with stories, or have a way to detect what file(s)
changed and run the appropriate stories, or because they're
integration tests, would it just re-
Just found answer to one of my questions below on being able to run
stories in TextMate. The new bundle for stories looks cool:
http://github.com/bmabey/rspec-story-tmbundle/tree/master
On Thu, Jun 19, 2008 at 9:56 AM, Christopher Bailey
<[EMAIL PROTECTED]> wrote:
> Kyle, thanks much for sharing
On 19-Jun-08, at 9:10 AM, Kyle Hargraves wrote:
The typical cause of these infinite loops is that your test suite
updates some file in your project; autotest notices the change and
immediately starts again.
The solution is to simply add exceptions to your project's .autotest,
ignoring any files
Christopher Bailey wrote:
Just found answer to one of my questions below on being able to run
stories in TextMate. The new bundle for stories looks cool:
http://github.com/bmabey/rspec-story-tmbundle/tree/master
Hey Chris,
There is actually a bug for running the stories that accidentally g
Hello,
I'm creating a REST resource with the following map
*map.resources :books, :member => { :prices => :get }
*
I would like to test the books controller
*class BooksController < ApplicationController
def prices
render :text => "Test"
end
end*
I have the following test
*it "should r
Try this:
it "should render properly when getting /books/:id/prices" do
get "prices", :id => '0'
response.should be_success
end
Or even better (or what i think you wanted to do):
map.resources :books, :collection => { :prices => :get }
And your spec won't be changed.
On Thu, Jun 19, 2008 a
On Thu, Jun 19, 2008 at 12:32 PM, Lori M Olson <[EMAIL PROTECTED]> wrote:
> Would you have an example of such an exception to share?
>
> Thanks, Lori
The .autotest at the base of one of my plugins, which updates a .sqlite3:
Autotest.add_hook :initialize do |at|
at.add_exception('spec/db/tracks_
12 matches
Mail list logo
