On 21 Oct 2008, at 15:47, Joseph Wilk wrote:
Would you mind creating a ticket for it in lighthouse please?
Sure, that's the easy part ;)
http://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/57-scenario-templates-to-allow-for-terse-scenario-tables
Hi,
I'm facing an issue with cucumber: when calling 'rake features' I get
an uninitialized constant Dispatcher (full stacktrace here:
http://pastie.org/297842).
I'm using Rails 2.0.5, the latest webrat/cucumber/rspec/rspec-rails.
Did anyone meet this issue ?
cheers,
Thibaut
--
http://evolvingw
On 21 Oct 2008, at 22:13, Stephen Eley wrote:
On Tue, Oct 21, 2008 at 3:57 PM, Rahoul Baruah <[EMAIL PROTECTED]>
wrote:
* the presenter/service's role is to coordinate the models - so its
specs
are purely about mocking the associations and the calls inbetween
them
* the presenter/service i
On 21 Oct 2008, at 19:51, David Chelimsky wrote:
Hey all,
Just a heads up about a bug related to configuring the rspec gems in
your rails 2.1.1 projects:
I had a little crack at this, but I got scared off as there seems to
be some chicken-and-egg stuff going on. My rake tasks require rspec,
On Wed, Oct 22, 2008 at 4:48 AM, Matt Wynne <[EMAIL PROTECTED]> wrote:
> On 21 Oct 2008, at 19:51, David Chelimsky wrote:
>
>> Hey all,
>>
>> Just a heads up about a bug related to configuring the rspec gems in
>> your rails 2.1.1 projects:
>
> I had a little crack at this, but I got scared off as
On 22 Oct 2008, at 10:58, Luis Lavena wrote:
On Wed, Oct 22, 2008 at 4:48 AM, Matt Wynne <[EMAIL PROTECTED]>
wrote:
On 21 Oct 2008, at 19:51, David Chelimsky wrote:
Hey all,
Just a heads up about a bug related to configuring the rspec gems in
your rails 2.1.1 projects:
I had a little crack
On Tue, Oct 21, 2008 at 9:39 PM, Harry Bishop <[EMAIL PROTECTED]> wrote:
> Thanks David,
> Your method works well and rspec succeeds now.
>
> Is the preferred way of using code with rspec to not rely on instance
> variables set in a parent during execution but to rely on the method
> only construct
On Sun, Oct 19, 2008 at 9:44 PM, Scott Taylor
<[EMAIL PROTECTED]> wrote:
>
> On Oct 19, 2008, at 12:14 PM, Pat Maddox wrote:
>
>> Scott Taylor <[EMAIL PROTECTED]> writes:
>>
>>> On Oct 18, 2008, at 9:19 AM, Pat Maddox wrote:
>>>
Scott Taylor <[EMAIL PROTECTED]> writes:
> As for #3, I'
David Chelimsky wrote:
> On Tue, Oct 21, 2008 at 9:39 PM, Harry Bishop <[EMAIL PROTECTED]>
> wrote:
>> approach you are providing would indicate that an attr_read method is
>> preferred so that the retrieve method can be stubbed since the instance
>> variable doesn't get set when tested.
>>
>> Is
On Oct 22, 2008, at 9:46 AM, David Chelimsky wrote:
On Sun, Oct 19, 2008 at 9:44 PM, Scott Taylor
<[EMAIL PROTECTED]> wrote:
On Oct 19, 2008, at 12:14 PM, Pat Maddox wrote:
Scott Taylor <[EMAIL PROTECTED]> writes:
On Oct 18, 2008, at 9:19 AM, Pat Maddox wrote:
Scott Taylor <[EMAIL PROTE
On Oct 21, 2008, at 7:24 am, Jarkko Laine wrote:
Yeah, I was using that API to a great extent with a recent project
and was pretty successful at doing outside-in development with rspec
and merb. The syntax used in merb controller specs is a bit
different from what Rails uses, but once you
Matt Wynne <[EMAIL PROTECTED]> writes:
> If we assume that the work to be done against the database or other
> sub-systems is non-trivial, then we should not directly call the
> persistence layer (= Models in Railsspeak) from the Controller, but
> delegate that to another class. It seems like Serv
12 matches
Mail list logo
