On 9/22/07, Andrew WC Brown <[EMAIL PROTECTED]> wrote:
> I've written a story and I run into a snag.
> I've written the create_forum method and told it to set the id to 1
> but when it creates the forum the id is autoincremented.
> My forums table is empty but the id keeps incrementing the newest r
I've written a story and I run into a snag.
I've written the create_forum method and told it to set the id to 1
but when it creates the forum the id is autoincremented.
My forums table is empty but the id keeps incrementing the newest record on
creation.
When I run the story it comes out as somethi
I'm currently in a simliar situation as you.
I have an application that doesn't use the default routing.
When I try to write my stories.
ex.
And "user logged in successfully" do
post "/session/create", :login => "Jon", :password => "your_momma"
response.should redirect_to(home_path)
end
The
Controller specs are similar to Rails functional tests, except that
they don't render views (unless you tell them to). So rather than
saying:
get notes_path(1,1)
you want to say:
get :show, :writer_id => "1", :note_id => "1"
Give that a shot and let us know if it works out.
Cheers,
David
On 9
Hi all,
The app I am making right now uses restful routing entirely. I want to
prevent people from accessing my actions without the proper HTTP verb so
I commented out the :controller/:action/:id catch all routes that were
used in pre-RESTful Rails apps. Like so:
#map.connect ':controller/:
On 9/22/07, Doug Wright <[EMAIL PROTECTED]> wrote:
> I apologize if this is a very dumb newbie issue, but I really want to
> experiment with the new "Story Runner" functionality in rspec and I'm having
> trouble using the trunk.
>
> I've tried in both windows and linux environments and have differe
I apologize if this is a very dumb newbie issue, but I really want to
experiment with the new "Story Runner" functionality in rspec and I'm having
trouble using the trunk.
I've tried in both windows and linux environments and have different
problems on each.
On linux, I execute svn co svn://rubyf
> * I mentioned how Test::Unit development had stagnated, and they took a
> different view of it: Test::Unit is "complete". It's done, it works,
> it provides a base level of functionality that doesn't need any more
> updating.
That's quite troubling in my opinion for a developer(s) to say that
On 9/21/07, Andrew WC Brown <[EMAIL PROTECTED]> wrote:
> I'm trying to generate stories based on Dan North's example.
> I'm not sure how to do this.
>
> require File.join(File.dirname(__FILE__), "helper")
>
> Story "Account Holder withdraws cash", %{
> As an Account Holder
> I want to withdraw
Hi all,
I'm having very odd behavior, but only with a few of my specs.
I'm checking the value of response.body and in most cases finding it
to be the content of the body... but in some cases it's the name of
the template rendered!! There's no rhyme or reason I can see, but
obviously my test
Hi Peter,
I ended up settling on having a "ensure_goldberg_loaded" helper in
spec_helper and a login_as that "spoofs" the session in the way that
set_user would do but without relying on Goldberg. This should make
it less coupled with Goldberg and let you test your code without
testing gol
I tend to write a fresh description block for every change in the parameters
for that specific action, because I hate conditionals in the example
describtion, e.g.:
describe SomeController, "handling GET /path/with/param/3" do
it "should do this"
it "should not do this if"
it "should still do th
12 matches
Mail list logo
