Guys,
This could be me, but I thought I'd check
For some reason, when I spec controllers, I run into this problem
(intermittently it would seem). Right now, I have a spec that fails
predictably.
I'm using
* Rspec 2.4.0
* Rspec-rails 2.4.1
* Rails 3
* Mocha 0.9.10
I have the following defined in
In RSpec 1.x, a print statement in the spec would print out with the
results from that spec. In RSpec 2.x, the print statements are
separated from the spec results. Is there a way to restore the 1.x
behavior, so quick debugging work we do with print statements can
easily be associated with the te
On Jan 12, 2011, at 9:52 AM, Chuck Remes wrote:
>
> On Sep 30, 2010, at 10:06 AM, GregD wrote:
>
>> Hi all,
>>
>> I'm testing java classed using rspec and jruby. The java super class
>> is trapping an exception and sending a custom message to stdout along
>> with the original exception meaasa
Why not stub System.out.println, possibly with message expectations if
necessary?
>
> On Sep 30, 2010, at 10:06 AM, GregD wrote:
>
>> Hi all,
>>
>> I'm testing java classed using rspec and jruby. The java super class
>> is trapping an exception and sending a custom message to stdout along
>> with
I am using rspec-rails 2.4.1 on a rails3 (3.0.3) app. I have around 20
specs. When I run rake spec all 20 specs run fine.
However when I do bundle exec rspec then I get this message.
No examples were matched. Perhaps {:unless=>#, :if=>#} is excluding everything?
__
Excerpts from Chuck Remes's message of Wed Jan 12 07:52:58 -0800 2011:
> I'd like to bump this message because I am facing a similar situation.
>
> What's a good technique for spec'ing code that prints to STDOUT yet keeps the
> spec output nice and clean?
I can't promise that what follows is a
On Sep 30, 2010, at 10:06 AM, GregD wrote:
> Hi all,
>
> I'm testing java classed using rspec and jruby. The java super class
> is trapping an exception and sending a custom message to stdout along
> with the original exception meaasage. The original exception is a
> SAXParseException, if that
Thanks a lot.Will look into it.
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
Hi,
On Wed, Jan 12, 2011 at 15:45, Amit Kulkarni wrote:
> When running the script i am getting output as
> User Profile should not be created if name is blank
> Failure/Error: @contact_detail.should be_valid
> expected valid? to return true, got false
> # ./spec/models/merchant_spec
On Tue, Jan 11, 2011 at 17:33, David Chelimsky wrote:
>
> On Jan 10, 2011, at 8:27 AM, Marko Anastasov wrote:
>
>> On Mon, Jan 10, 2011 at 05:05, David Chelimsky wrote:
>>> On Jan 5, 2011, at 11:54 AM, Marko Anastasov wrote:
>>>
Hello,
I set a value in controller spec using @request
On Wed, Jan 12, 2011 at 09:19, Amit Kulkarni wrote:
> Hi,
> I have successfully installed rspec 2 for Rails 3 by visiting the
> following link
> http://lindsaar.net/2010/4/14/installing_rspec_for_rails_3
> In this post it is mentioned taht when i do "rails g rspec:install"
> then it should instal
Hi,
I have successfully installed rspec 2 for Rails 3 by visiting the
following link
http://lindsaar.net/2010/4/14/installing_rspec_for_rails_3
In this post it is mentioned taht when i do "rails g rspec:install"
then it should install
exist lib
create lib/tasks/rspec.rake
exist con
Hi,
I am running rspec spec for Rails 3.The version for rspec is 2.4.0
When running the script i am getting output as
User Profile should not be created if name is blank
Failure/Error: @contact_detail.should be_valid
expected valid? to return true, got false
# ./spec/models/merchan
13 matches
Mail list logo
