I believe this is caused by a bad example on
https://github.com/rspec/rspec/wiki/autotest
,specifically under the section "Advanced autotest configuration".
I ran into this exact same issue and it was solved by changing the
example to use spec/**/*_spec.rb.
I went ahead and took the liberty of u
On Thu, Feb 3, 2011 at 1:40 PM, David Kahn wrote:
> This came up from an other issue where I needed to go check something in
> test::unit. Immediately when I dropped into the debugger in test::unit I saw
> something I have been missing: test unit by default shows a number of lines
> of code. Is th
On Thu, Feb 3, 2011 at 11:24 AM, David Chelimsky wrote:
> On Feb 3, 2011, at 11:04 AM, David Kahn wrote:
>
>
>
> On Thu, Feb 3, 2011 at 10:32 AM, David Chelimsky wrote:
>
>> On Feb 3, 2011, at 9:28 AM, David Kahn wrote:
>>
>> On Thu, Feb 3, 2011 at 8:48 AM, Scott Taylor wrote:
>>
>>>
>>> Probably
This came up from an other issue where I needed to go check something in
test::unit. Immediately when I dropped into the debugger in test::unit I saw
something I have been missing: test unit by default shows a number of lines
of code. Is there a way to make the rspec debugger do this?
I am not sur
On Feb 3, 2011, at 12:04 PM, David Kahn wrote:
>
>
> On Thu, Feb 3, 2011 at 10:32 AM, David Chelimsky wrote:
> On Feb 3, 2011, at 9:28 AM, David Kahn wrote:
>
>> On Thu, Feb 3, 2011 at 8:48 AM, Scott Taylor wrote:
>>
>> Probably manually rescuing your debugger call would work:
>>
>> begin
On Feb 3, 2011, at 11:04 AM, David Kahn wrote:
>
>
> On Thu, Feb 3, 2011 at 10:32 AM, David Chelimsky wrote:
> On Feb 3, 2011, at 9:28 AM, David Kahn wrote:
>
>> On Thu, Feb 3, 2011 at 8:48 AM, Scott Taylor wrote:
>>
>> Probably manually rescuing your debugger call would work:
>>
>> begin
>
On Thu, Feb 3, 2011 at 10:32 AM, David Chelimsky wrote:
> On Feb 3, 2011, at 9:28 AM, David Kahn wrote:
>
> On Thu, Feb 3, 2011 at 8:48 AM, Scott Taylor wrote:
>
>>
>> Probably manually rescuing your debugger call would work:
>>
>> begin
>> debugger
>> rescue Exception
>> end
>>
>
> Thanks, I jus
On Feb 3, 2011, at 9:28 AM, David Kahn wrote:
> On Thu, Feb 3, 2011 at 8:48 AM, Scott Taylor wrote:
>
> Probably manually rescuing your debugger call would work:
>
> begin
> debugger
> rescue Exception
> end
>
> Thanks, I just tried this but no go, the rspec still trips and fails me out.
> M
On Thu, Feb 3, 2011 at 8:48 AM, Scott Taylor wrote:
>
> Probably manually rescuing your debugger call would work:
>
> begin
> debugger
> rescue Exception
> end
>
Thanks, I just tried this but no go, the rspec still trips and fails me out.
Maybe I have a really different methodology but I depend
Probably manually rescuing your debugger call would work:
begin
debugger
rescue Exception
end
Scott
On Feb 3, 2011, at 9:18 AM, David Kahn wrote:
> I am curious as with Test::Unit I could go into the debugger and stay all day
> inside of a test and make all kinds of errors without a problem
I am curious as with Test::Unit I could go into the debugger and stay all
day inside of a test and make all kinds of errors without a problem. With
rspec I experience that if I make a bad query/ActiveRecord call that it
flips out and fails the test, throwing me back to the command prompt. This
is n
Hi
Since rails 3 all strings are escaped, unlike rails 2 where you had to use the
h method
use .html_safe in your helper method to stop the output escaping
the test is correct
This article will explain a little bit more
http://markconnell.co.uk/posts/2010/02/rails-3-html-escaping
--
Rob Aldred
12 matches
Mail list logo
