On 25/02/2008, at 11:42 , David Chelimsky wrote:
> Steve - it's because of isolation - I pointed Alex to the docs.
Yup, I'm having a low-caffeine day apparently. I'm going to great
pains to isolate just the portions of the controller that need to be
designed (using mocks and stubs), then slap
On Sun, Feb 24, 2008 at 6:35 PM, s.ross <[EMAIL PROTECTED]> wrote:
> On Feb 24, 2008, at 4:29 PM, Alex Satrapa wrote:
>
> > Okay, this is weird. The result seems to indicate that the body of
> > the response is the literal text, "resource/new":
> >
> > My autotest results show (I've changed th
On Feb 24, 2008, at 4:29 PM, Alex Satrapa wrote:
> Okay, this is weird. The result seems to indicate that the body of
> the response is the literal text, "resource/new":
>
> My autotest results show (I've changed the name of the resource to
> 'resource'):
>>
Try
puts response.class
puts respons
On Sun, Feb 24, 2008 at 6:29 PM, Alex Satrapa <[EMAIL PROTECTED]> wrote:
> On 25/02/2008, at 10:58 , David Chelimsky wrote:
>
> > On Sun, Feb 24, 2008 at 5:54 PM, Alex Satrapa
> > <[EMAIL PROTECTED]> wrote:
>
> >> In the ResourceController spec, I have the following happening:
> >> post( :
On 25/02/2008, at 10:58 , David Chelimsky wrote:
> On Sun, Feb 24, 2008 at 5:54 PM, Alex Satrapa
> <[EMAIL PROTECTED]> wrote:
>> In the ResourceController spec, I have the following happening:
>> post( :create, :resource => request_attrs )
>> response.should render_template('resource/
On Sun, Feb 24, 2008 at 5:54 PM, Alex Satrapa <[EMAIL PROTECTED]> wrote:
> In a story, I have the following happening:
> post("/resources/", 'resource' => request_attrs)
> response.should render_template('resource/new')
> response.should have_tag('*', /must have one or more X defined
In a story, I have the following happening:
post("/resources/", 'resource' => request_attrs)
response.should render_template('resource/new')
response.should have_tag('*', /must have one or more X defined/)
In the ResourceController spec, I have the following happening:
post( :c
>At first glance, that is really cool. We've also batted around some
>other names like #facet or #behavior.
LOL..I smile because we went through the same semantic struggles as well.
The funny thing is the rSpec project led us to our resolve. :-)
We basically came to this conclusion every object
On Sun, Feb 24, 2008 at 5:29 AM, Joe Ocampo <[EMAIL PROTECTED]> wrote:
> Background just started programming in Ruby literally 12 hours ago and have
> a question regarding context and describe methods. Reading the RDoc it
> indicated that "context" is an alias for "describe". So I decided to try
Background just started programming in Ruby literally 12 hours ago and have
a question regarding context and describe methods. Reading the RDoc it
indicated that "context" is an alias for "describe". So I decided to try to
the following syntax seeing this is how I would approach it in C# with
NB
10 matches
Mail list logo
