hello,
when running rake spec, I'm getting a stack trace similar to the one
mentioned in this ticket, which has been resolved:
http://rspec.lighthouseapp.com/projects/5645/tickets/237
but from what I understood, if the project is using rspec 1.1.3 (as is
the case with mine), this shouldn't be ha
Hi Namrata,
thanks, that's a great resource and I ended up beefing my tests based
on the recommendations there.
actually though, the problem I was having was that validations weren't
being recognized by the test suite. later I found out that when
regenerating the scaffold for the app a while back
Hi,
We've been building plugins for our app, and we kept running into forgetting
to run the plugin specs when we updated from svn. So, I took the task on to
have the rake spec command include our plugin specs, as well. I only wanted
to have our plugin specs run, not third party ones.
In order to
Thanks for your help.
I tried the controller.stub!(...) as well, and it doesn't work.
Ivo I totally agree with you and I'll follow your recommendations,
thanks.
(Would still be nice to know if the stubbing could work or if it's
intended not to)
On Mar 6, 4:27 pm, Ivo Dancet <[EMAIL PROTECTED]> w
On Thu, Mar 6, 2008 at 7:27 AM, Ivo Dancet <[EMAIL PROTECTED]> wrote:
> You should not stub the authentication method in a story. The story
> should test the whole application framework, that way your story might
> look like this:
>
> Given a user from company x
> When logging in
> And request
You should not stub the authentication method in a story. The story
should test the whole application framework, that way your story might
look like this:
Given a user from company x
When logging in
And requesting some page
Then the application should do all the stuff it should
In the given s
On Thu, Mar 6, 2008 at 7:23 AM, Pat Maddox <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 6, 2008 at 7:12 AM, Bastien <[EMAIL PROTECTED]> wrote:
> > Thanks David, this works just fine. I would rather do some stubbing
> > there if it's possible though. I tried :
> >
> > ApplicationController.stub!
>
On Thu, Mar 6, 2008 at 5:50 AM, David Chelimsky <[EMAIL PROTECTED]> wrote:
>
> On Thu, Mar 6, 2008 at 1:01 AM, Pat Maddox <[EMAIL PROTECTED]> wrote:
> >
> > > > >>> On Wed, Mar 5, 2008 at 12:28 PM, Rick DeNatale <[EMAIL
> PROTECTED]
> > > > wrote:
> > > > So I want to write
On Thu, Mar 6, 2008 at 7:12 AM, Bastien <[EMAIL PROTECTED]> wrote:
> Thanks David, this works just fine. I would rather do some stubbing
> there if it's possible though. I tried :
>
> ApplicationController.stub!
> (:user_authentication_required).and_return(true)
try
controller.stub!()
Pat
Thanks David, this works just fine. I would rather do some stubbing
there if it's possible though. I tried :
ApplicationController.stub!
(:user_authentication_required).and_return(true)
(which is the filter called before each action that checks whether the
user is logged in or not)
But it doesn't
I think you can also use:
post "/authentication/login",
{ :login => user_email,
:password => password },
:host => "company.example.com"
Op 5-mrt-08, om 23:30 heeft Bastien het volgende geschreven:
> I've just begin using rspec stories, and i m encountering some
> problems. In my applica
On Wed, Mar 5, 2008 at 4:30 PM, Bastien <[EMAIL PROTECTED]> wrote:
> I've just begin using rspec stories, and i m encountering some
> problems. In my application i have different subdomains in which
> specific users can log in, for example an admin will go to
> admin.myapp.com/authenticate/login
I've just begin using rspec stories, and i m encountering some
problems. In my application i have different subdomains in which
specific users can log in, for example an admin will go to
admin.myapp.com/authenticate/login, and an user belonging to a
specific company will log in company.myapp.com/au
On Thu, Mar 6, 2008 at 1:21 AM, Ben Mabey <[EMAIL PROTECTED]> wrote:
>
> Pat Maddox wrote:
> > On Wed, Mar 5, 2008 at 4:22 PM, Rick DeNatale <[EMAIL PROTECTED]> wrote:
> >
> >> On 3/5/08, David Chelimsky <[EMAIL PROTECTED]> wrote:
> >> > On Mar 5, 2008, at 2:57 PM, "Rick DeNatale" <[EMAIL PROT
On Thu, Mar 6, 2008 at 1:01 AM, Pat Maddox <[EMAIL PROTECTED]> wrote:
>
> On Wed, Mar 5, 2008 at 4:22 PM, Rick DeNatale <[EMAIL PROTECTED]> wrote:
> >
> > On 3/5/08, David Chelimsky <[EMAIL PROTECTED]> wrote:
> > > On Mar 5, 2008, at 2:57 PM, "Rick DeNatale" <[EMAIL PROTECTED]>
> > >
> > >
On Thu, Mar 6, 2008 at 12:52 AM, Zach Dennis <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 5, 2008 at 12:28 PM, Rick DeNatale <[EMAIL PROTECTED]> wrote:
>
> > I'm wanting to write a spec that a model is applying an :order option
> > to a find call, but I don't want to completely specify all of the fin
Hi Namrata,
I recently ran into the same problem as well. The trick was to do
something like:
response.should have_rjs(some_arguments)
The 'some_arguments' threw me off for a while but I believe you
need :chained_replace_html.
I wrote a little piece on it here:
http://www.rubytutorials.net
17 matches
Mail list logo
