Hi,
Oh, I should have thought of that. Thanks a lot.
I'm growing used to the assert_xhtml syntax, lol, so I've just been using
that. Thank you though for fixing the be_html_with syntax.
Brandon
> -Original Message-
> From: rspec-users-boun...@rubyforge.org [mailto:rspec-users-
> boun...
assert_xhtml output do
div.error do
p 'Block'
end
end
Nokogiri has some "easter eggs" in its ambitious HTML::Builder system. One of
them is only HTML tags not already recognized as methods can get turned into
HTML tags. The usual .method_missing(
Hi,
Well, I googled some more, and everything I could find used eval_erb. So is
this the best method for testing helpers with blocks?
And then why is that block displaying when I run the test?
Thanks,
Brandon
> -Original Message-
> From: Brandon Olivares [mailto:programmer2...@gmail.com
On Wed, Apr 8, 2009 at 9:22 PM, danielpennypacker
wrote:
>
> So me and the senior dev solved the problem. We tried a number of things, so
> I'm not sure if my original question is that relevant, but here's what was
> kinda going on...
>
> -This is my first time integrating lots of plugins from ano
So me and the senior dev solved the problem. We tried a number of things, so
I'm not sure if my original question is that relevant, but here's what was
kinda going on...
-This is my first time integrating lots of plugins from another app, so I
was going in between installing gems as gems and inst
I'm starting one of these too... I'll github it when I'm happy with my
approach.
2009/4/8 Ben Mabey
> David Chelimsky wrote:
>
>> On Tue, Apr 7, 2009 at 3:26 PM, Sophie (itsme213)
>> wrote:
>>
>>
>>> Some time ago I had come across a web-based story editor for scenarios.
>>> I'm
>>> not sure if
Hey Tim,
I didn't see the first post.
If you've namespaced the controller, you'll need to make that change
in the spec.
My assumption is that
SponsorsController became Admin::SponsorsController
So you'll need to make sure that this is reflected in your spec.
-Jim
On Apr 8, 2009, at 5:18 PM,
On Wed, Apr 8, 2009 at 5:18 PM, TimBooher wrote:
> any takers? am i asking a question that is too hard or too easy and
> boring?
So your SponsorsController exists inside of a Admin module namespace?
If so update your spec:
describe Admin::SponsorsController
If that's not the issue I'm not q
any takers? am i asking a question that is too hard or too easy and
boring?
thanks,
tim
On Apr 7, 7:41 am, Tim Booher wrote:
> I am trying to get my workflow down and am confused on several fronts. The
> first is how to get my rspec_scaffold tests to run. The problem is that i
> generated my sc
All,
I know this is an older post but I have a similar but different set of
scenarios I need to handle. I have a set of flight related scheduling
features, such as delay, reschedule, and cancel, each with multiple
scenarios that have an effect on later flights in the schedule (there
are a lot
On Wed, Apr 8, 2009 at 2:08 PM, doug livesey wrote:
> Hi, after an update to all the latest gems, I have a controller spec failing
> that wasn't previously:
> flash[:alert].should eql( "Blah blah." )
>
> The flash is being set by "flash.now[:alert] = '...'" in this instance.
> Can anyone sugges
On 7 Apr 2009, at 17:23, Scott Taylor wrote:
On Apr 7, 2009, at 11:54 AM, Ben Mabey wrote:
On Apr 7, 2009, at 8:30 AM, aidy lewis wrote:
On 07/04/2009, Zach Dennis wrote:
On Mon, Apr 6, 2009 at 12:21 PM, Ben Mabey
wrote:
My best
suggestion would be to set multiple breakpoints and h
On Wed, Apr 8, 2009 at 12:07 PM, Sven wrote:
>> In general, I write before()
>> after I write the examples, since I usually consider it just a DRY
>> refactoring.
>
> Good point. I guess I'll just get used to it then :-)
No, please don't get used to it. The behaviour you expect is correct,
and th
Thanks David,
It seems like remarkable was the culprit. Somebody had posted the same issue
to lighthouse.
The solution was to specify the lib in environment.rb instead of setting it
to false for rspec and rspec-rails. The discussion was in Portuguese so I'm
not sure why this works.
I don't get
Hi. Bira -- just got the same problem myself, and have found that (whilst
not a perfect solution) that stubbing out render on the controller in my
before block solves it.
controller.stub!( :render )
HTH,
Doug.
2009/4/1 Bira
> I'm trying to upgrade to RSpec 1.2.2 in a Rails app, and reading
>
Hi, after an update to all the latest gems, I have a controller spec failing
that wasn't previously:
flash[:alert].should eql( "Blah blah." )**
The flash is being set by "flash.now[:alert] = '...'" in this instance.
Can anyone suggest how I can make this work again?
Cheers,
Doug.
___
Oops, sotty about that, I got my version of ruby mixed in there.
They're both 1.1.8
I followed the instructions here:
http://wiki.github.com/dchelimsky/rspec/rails
David Chelimsky-2 wrote:
>
> On Tue, Apr 7, 2009 at 6:55 PM, danielpennypacker
> wrote:
>>
>> We're using Rails 2.1.1 and rspec/
On Apr 8, 2009, at 11:09 AM, Andrea Jahn wrote:
Hi,
I added one line in my controller to extend the params hash. But now
I get errors
in my controller spec.
Controller
def update
@pl_planning = PlPlanning.find(params[:id])
# the item model version (select box) depends on other
On Wed, Apr 8, 2009 at 6:11 AM, Sven wrote:
> I've noticed that pending expectations fail if the before(:each) code is not
> implemented yet. In other words, taking the example code from Peepcode's rspec
> series:
>
> describe Weather, ".fetch for zipcode" do
>
> before(:each) do
> �...@weather
Hi,
I added one line in my controller to extend the params hash. But now I get
errors
in my controller spec.
Controller
def update
@pl_planning = PlPlanning.find(params[:id])
# the item model version (select box) depends on other select boxes and can be
empty
# then it is not in the
> In general, I write before()
> after I write the examples, since I usually consider it just a DRY
> refactoring.
Good point. I guess I'll just get used to it then :-)
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/
On Wed, Apr 8, 2009 at 11:59 AM, Mark Wilden wrote:
> On Wed, Apr 8, 2009 at 2:11 AM, Sven wrote:
>
>> describe Weather, ".fetch for zipcode" do
>>
>> before(:each) do
>> �...@weather = Weather.fetch_for_zipcode(98117)
>> end
>>
>> it "should populate zipcode"
>>
>> it "should populate temp
On Wed, Apr 8, 2009 at 2:11 AM, Sven wrote:
> describe Weather, ".fetch for zipcode" do
>
> before(:each) do
> �...@weather = Weather.fetch_for_zipcode(98117)
> end
>
> it "should populate zipcode"
>
> it "should populate temperature units"
>
> it "should populate recorded at"
>
> end
>
>
Hi,
I am trying to write and test a helper that accepts a block. Right now it
goes something like this:
module ContactHelper
# Wraps a field with div.error if it has an error.
def wrap_error_field errors, &block
field = capture &block
if errors.empty?
concat field
else
I've noticed that pending expectations fail if the before(:each) code is not
implemented yet. In other words, taking the example code from Peepcode's rspec
series:
describe Weather, ".fetch for zipcode" do
before(:each) do
@weather = Weather.fetch_for_zipcode(98117)
end
it "should popu
On 7 Apr 2009, at 22:19, aslak hellesoy wrote:
Ben Mabey has accepted my invitation to be on the core Cucumber team.
Ben has been a long time contributor to Cucumber's ecosystem and
knows it inside out.
Here is a quote from IRC today:
mabes: Yeah but you're the cucumber God.
The core Cuc
aslak hellesoy wrote:
Ben Mabey has accepted my invitation to be on the core Cucumber team.
Ben has been a long time contributor to Cucumber's ecosystem and knows
it inside out.
Here is a quote from IRC today:
mabes: Yeah but you're the cucumber God.
The core Cucumber team now consists of J
27 matches
Mail list logo
