Hi folks,
I'm somewhat new to the current RSpec release - at work we are still
using 0.8.something, with "context 'blah' do ... specify 'should
thing' ..."
We have some helper code to automatically mix-in selenium:
module SeleniumHelper
include SpecHelper
...
def initialize(arg)
@selenium
Have you tried just turning @selenium into a method for lazy
initialization? So, you could have:
def selenium
@selenium ||= SeleniumHelper.selenium
end
The in your spec just use the method call as opposed to the instance
variable.
That is probably what I would do. I have never used in
Hi,
I saw a previous post from David answering someones question about
fixture_scenarios with rspec. Following that I upgraded my rspec and
rspec_on_rails to the trunk versions and then installed the fixture
scenario plugin.
Now whenever I run my (previously passing rspecs) I get the follow
In my rspec_on_rails controlle rspec, I have this:
require File.dirname(__FILE__) + '/../spec_helper'
describe FooController, "with a foo" do
it "should be false" do
get 'index'
assigns[:foo].should be_false
end
end
In my controller I have this:
class FooController < ApplicationCon
Just started looking at the Story Runner integration, and am
converting a few Rails integration tests to get a feel for it.
My integration tests relied on fixtures, and since my models have a
significant amount of validation (and hence need valid data unless I
save without validation), this
I figured it out.
By doing this session sanity check in the spec (as recommended by
dchelimsky):
sess = session
get 'index'
sess.should equal(session)
I was able to see that a 'Please log in' redirect was preventing index from
getting called.
Chad
cnantais wrote:
>
> In my rspe
On 9/26/07, Simon Peter Nicholls <[EMAIL PROTECTED]> wrote:
> Just started looking at the Story Runner integration, and am
> converting a few Rails integration tests to get a feel for it.
>
> My integration tests relied on fixtures, and since my models have a
> significant amount of validation (and
When I untar 1.0.8 after having downloaded it from rubyforge, I get
these errors:
rspec-1.0.8/spec/spec/runner/spec_parser_spec.rb
rspec-1.0.8/spec/spec/spec_classes.rb
gzip: stdin: decompression OK, trailing garbage ignored
rspec-1.0.8/spec/spec/translator_spec.rb
rspec-1.0.8/spec/spec_helper
Do I have to create a custom Expectation Matcher?
or there is a way to integrate assert_valid_asset plugin?
thx
--
Edgar González González
--
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
On 9/27/07, Edgar Gonzalez <[EMAIL PROTECTED]> wrote:
> Do I have to create a custom Expectation Matcher?
>
> or there is a way to integrate assert_valid_asset plugin?
>
> thx
> --
> Edgar González González
> --
> ___
> rspec-users mailing list
> rspec-us
Thanks Pat! I find your arguments fairly compelling.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
On Sep 27, 2007, at 12:41 PM, Pat Maddox wrote:
> On 9/26/07, Simon Peter Nicholls <[EMAIL PROTECTED]> wrote:
>> Just started looking at the Story Runner integration, and am
>> converting a few Rails integration tests to get a feel for it.
>>
>> My integration tests relied on fixtures, and since m
On 9/27/07, Christopher D. Pratt <[EMAIL PROTECTED]> wrote:
> I recently post on my blog about setting up a Rails environment with RSpec
> in Windows, and someone left a comment saying that it doesn't work in
> EdgeRails. I so I played around with it a bit and was able to confirm that
> none RSpec
On 9/27/07, Christopher D. Pratt <[EMAIL PROTECTED]> wrote:
> I recently post on my blog about setting up a Rails environment with RSpec
> in Windows, and someone left a comment saying that it doesn't work in
> EdgeRails. I so I played around with it a bit and was able to confirm that
> none RSpec
This was a known problem. I believe it should be fixed in the next
release (fixed on trunk).
Scott
On Sep 27, 2007, at 3:53 PM, barsalou wrote:
> When I untar 1.0.8 after having downloaded it from rubyforge, I get
> these errors:
>
>
>
> rspec-1.0.8/spec/spec/runner/spec_parser_spec.rb
> r
I second that ;). Thanks Luis. Never ceases to amaze me how quickly people
on this list respond. Thanks to all of you for all the support.
As for my problem, I'll give what you said a try. It makes sense, so I doubt
I'll have any further problems.
Thanks again,
Chris Pratt
On 9/27/07, Luis Lave
I recently post on my blog about setting up a Rails environment with RSpec
in Windows, and someone left a comment saying that it doesn't work in
EdgeRails. I so I played around with it a bit and was able to confirm that
none RSpec appears broken on EdgeRails. I'll post the various error messages
I
On 9/27/07, Luis Lavena <[EMAIL PROTECTED]> wrote:
> On 9/27/07, Christopher D. Pratt <[EMAIL PROTECTED]> wrote:
> > I recently post on my blog about setting up a Rails environment with RSpec
> > in Windows, and someone left a comment saying that it doesn't work in
> > EdgeRails. I so I played arou
On Thu, 2007-09-27 at 16:07 -0400, Edgar Gonzalez wrote:
> Do I have to create a custom Expectation Matcher?
>
> or there is a way to integrate assert_valid_asset plugin?
>
> thx
I'm using this expectation to check for valid XHTML using a locally
installed copy of tidy: http://pastie.caboo.se/10
19 matches
Mail list logo
