Hmm - on digging further, I might be better off writing a custom formatter
as described at
http://wiki.github.com/aslakhellesoy/cucumber/custom-formatters, and just
invoking cucumber with --dry-run and my formatter... Though as I want to
use the html formatter to format steps for insertion into th
On Tue, Apr 7, 2009 at 2:19 PM, 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.
>
Cool! Congrats Ben.
On Tue, Apr 7, 2009 at 6:13 PM, Zach Dennis wrote:
> On Tue, Apr 7, 2009 at 5:53 PM, Ben Mabey wrote:
> > 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 a
On Tue, Apr 7, 2009 at 10:32 AM, James B. Byrne wrote:
>
> I have run into a minor glitch and would like to know what others
> think. I am working on a test/expectation and as part of the
> process of debugging I am rolling back db:migrations one step at a
> time to discover where the problem was
On Tue, Apr 7, 2009 at 6:55 PM, danielpennypacker
wrote:
>
> We're using Rails 2.1.1 and rspec/rspec_on_rails 1.8.6.
1.8.6 doesn't really exist. The most recent is 1.2.2 :)
> It was working okay
> on a different my dev branch, so I'm not sure if different versions are the
> problem.
>
> Thanks s
On Tue, Apr 7, 2009 at 6:20 PM, Andrew Zielinski
wrote:
>
> I hope somebody can help me with this.
>
> I can't seem to run spec_server with rails 2.3.2 using rspec/rspec-rails
> 1.2.2. I'm also using mocha 0.9.5 and remarkable 2.3.0.
The stack trace doesn't show it, but the superclass mismatch su
We're using Rails 2.1.1 and rspec/rspec_on_rails 1.8.6. It was working okay
on a different my dev branch, so I'm not sure if different versions are the
problem.
Thanks so much for the speedy reply, and I hope knowing my versions helps.
My senior dev is gonna help with it tomorrow, so I'll make
I hope somebody can help me with this.
I can't seem to run spec_server with rails 2.3.2 using rspec/rspec-rails
1.2.2. I'm also using mocha 0.9.5 and remarkable 2.3.0.
Thanks Andrew
Here is the stack trace:
-
/Library/Ruby/Gems/1.8/gems/rspec-rails-1.2.2/lib
Hi folks,
I'm writing some scripts to integrate our cucumber features with stories
stored in a wiki, and I'm hoping to use cucumber's parser to parse the
features rather than doing it manually. (I don't really care about the
feature contents much, just scenario titles and tags)
I've worked out ho
On Tue, Apr 7, 2009 at 5:53 PM, Ben Mabey wrote:
> 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
On Tue, Apr 7, 2009 at 5:40 PM, danielpennypacker
wrote:
>
> Here's an intro to what I'm working on...
>
> - We're adding Beast Forums to our site and we decided to integrate the code
> instead of have it run in a separate app.
>
> - Beast uses rspec, and this was the first time I've been exposed
Here's an intro to what I'm working on...
- We're adding Beast Forums to our site and we decided to integrate the code
instead of have it run in a separate app.
- Beast uses rspec, and this was the first time I've been exposed to it, we
use boring old unit tests. Beast also uses the rspec_on_ra
by the way, cool presentation at mountain west :-)
congrats
2009/4/7 Scott Taylor
>
> On Apr 7, 2009, at 5:19 PM, 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
>> insi
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 it was a full runner, and it was probably before cucumber.
Anyone know where I can find it?
It was only a protoype w
On Apr 7, 2009, at 5:19 PM, 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
On Tue, Apr 7, 2009 at 4:19 PM, 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.
>
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
On Apr 7, 2009, at 4:26 PM, Sophie (itsme213) wrote:
Some time ago I had come across a web-based story editor for
scenarios. I'm
not sure if it was a full runner, and it was probably before cucumber.
Anyone know where I can find it?
Aslak had a prototype a while back - although it was only
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 it was a full runner, and it was probably before cucumber.
>
> Anyone know where I can find it?
It was only a protoype with some javascript to make
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 Joseph Wilk, Ben Mabey and
Some time ago I had come across a web-based story editor for scenarios. I'm
not sure if it was a full runner, and it was probably before cucumber.
Anyone know where I can find it?
Thanks
___
rspec-users mailing list
rspec-users@rubyforge.org
http:/
On Tue, Apr 7, 2009 at 10:44 AM, Scott Taylor wrote:
>
> On Apr 7, 2009, at 1:32 PM, James B. Byrne wrote:
>
>>
>> I have run into a minor glitch and would like to know what others
>> think. I am working on a test/expectation and as part of the
>> process of debugging I am rolling back db:migrati
On Tue, Apr 7, 2009 at 12:08 PM, Peer Allan wrote:
> We found the issue and it was related to how rspec wraps assert_select. In
> rspec-rails 1.1.12 HTML::Document is initialized differently for
> response.body than for strings. In 1.2.2 this was changed so that they were
> initialized in the sa
We found the issue and it was related to how rspec wraps assert_select. In
rspec-rails 1.1.12 HTML::Document is initialized differently for
response.body than for strings. In 1.2.2 this was changed so that they were
initialized in the same way. This caused the string to be validated as XML
and ge
On Apr 7, 2009, at 1:32 PM, James B. Byrne wrote:
I have run into a minor glitch and would like to know what others
think. I am working on a test/expectation and as part of the
process of debugging I am rolling back db:migrations one step at a
time to discover where the problem was introduced
I have run into a minor glitch and would like to know what others
think. I am working on a test/expectation and as part of the
process of debugging I am rolling back db:migrations one step at a
time to discover where the problem was introduced.
My workflow looks like this:
$ cucumber ... featur
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 hit "c" to
continue to
the next one so you can
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 hit "c" to
continue to
the next one so you can skip through all of Cucumber's code.
I will s
On Tue, Apr 7, 2009 at 7:30 AM, aidy lewis wrote:
>
> Some useful tips, but I feel the ruby-debug tutorials that exist are
> lacking. Would it be fitting for me to add a Cucumber and ruby-debug
> page on the Wiki?
With webrat, the following is pretty useful:
When /^I view the response$/ do
sav
On Apr 7, 2009, at 7:47 AM, TimBooher 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 scaffold, then moved my controller into a
namespace named :admin.
So I have the followi
On Tue, Apr 7, 2009 at 4:30 PM, 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 hit "c" to
> continue to
> > > the next one so you can skip through all of Cu
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 scaffold, then moved my controller into a
namespace named :admin.
So I have the following familiar code. How can i change this to avoid:
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 scaffold, then moved my controller into a namespace named
:admin.
So I have the following familiar code. How can i change this to avoid:
> This is going to sound a lot like buck-passing, but the have_tag
> matcher in rspec-rails is a wrapper for Rails' assert_select, which is
> what does the actual parsing. So if the fix is to make it more
> tolerant of poorly formatted XHTML, that's going to have to go to the
> rails project.
>
Y
On Tue, Apr 7, 2009 at 8:47 AM, Peer Allan wrote:
> We are finally starting to narrow this down somewhat. Turns out we are
> getting the errors because the XHTML is invalid when it comes back from
> webrat/selenium.
>
> The specific problem right now happens when attempting to validate that
> the
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 hit "c" to continue to
> > the next one so you can skip through all of Cucumber's code.
> I will sometimes set a global variable to help
On Tue, Apr 7, 2009 at 4:11 PM, aslak hellesoy wrote:
>
>
> On Tue, Apr 7, 2009 at 2:50 PM, aslak hellesoy
> wrote:
>
>> There are a lot of open tickets in Cucumber, and it's hard for me to know
>> which ones to prioritize.
>> Several of them are either obsolete or not very important. I need your
On Tue, Apr 7, 2009 at 2:50 PM, aslak hellesoy wrote:
> There are a lot of open tickets in Cucumber, and it's hard for me to know
> which ones to prioritize.
> Several of them are either obsolete or not very important. I need your help
> to decide.
>
> I'm therefore going to put all tickets on hol
We are finally starting to narrow this down somewhat. Turns out we are
getting the errors because the XHTML is invalid when it comes back from
webrat/selenium.
The specific problem right now happens when attempting to validate that
there are x number of rows in a table. In a normal rspec view tes
There are a lot of open tickets in Cucumber, and it's hard for me to know
which ones to prioritize.
Several of them are either obsolete or not very important. I need your help
to decide.
I'm therefore going to put all tickets on hold. If you feel a particular
ticket should be reopened, please comm
David Chelimsky wrote:
it "should render" do
template.view_paths=(File.join(File.dirname(__FILE__),
"/../../../themes/my_theme/"))
render
end
And why isn't that DRY with the matching /../../../themes code on the
production side?
Because nobody has asked for support for views outside the
On Tuesday 07 April 2009, Phlip wrote:
> Michael Schuerig wrote:
> > def failure_message
> > "expected\...@raw_target}\n" +
> > "to be JSON code equivalent to\...@raw_expected}\n" +
> > "Difference:\...@expected.diff(@target).inspect}"
> > end
>
> Nice - this fix
42 matches
Mail list logo