Hi - sorry for the cross-list post, but this issue happens only with
cucumber and jruby, and I'm not 100% sure which has the problem. It
doesn't happen with non-j ruby though.
Versions:
cucumber 0.2.3
jruby 1.2.0 on Ubuntu amd64
When I have a cucumber feature with a "Then" step: (well, really
It's possibly worth pointing out for anyone else who needs to do
stubbing, that you don't necessarily need a framework to stub stuff; I
have cucumber tests that stub out some setup code in my app*, and they
just use monkey-patching to do the stubbing.
For instance, in the example below, you could
Celerity is very cool - when it works. It didn't work with out messy
combination of javascript libraries, alas. (Dojo 0.4-ish for legacy
bits, GWT for new bits) - apparently it will work with either of these
frameworks, but for us, with both, it died mysteriously (and we gave
up trying to fix it
equel library (
http://sequel.rubyforge.org/ ) , despite having a sucky name, is
*great* for this sort of thing - manipulating tables, one-off
migration scripts, and the like. If you need to manipulate data, but
don't want a full ORM, give it a look.
- Korny
On Thu, Apr 30, 2009 at 2:22 PM, Ben Mabey wro
cenarios as 'given' steps for others) but it's slower
- and the accumulated effect of slow builds can be terrible.
- Korny
On Thu, Apr 30, 2009 at 9:32 AM, Ben Mabey wrote:
> Korny Sietsma wrote:
>>
>> True, but cucumber is useful for lots of different kinds of proj
'm aware webrat works without rails, but when I looked it didn't
seem a big boost for our kind of app.
On Wed, Apr 29, 2009 at 10:42 PM, Chris Flipse wrote:
> On Wed, Apr 29, 2009 at 7:42 AM, Korny Sietsma wrote:
>>
>> Presumably you only need these if you are *building*
Presumably you only need these if you are *building* cucumber?
If you just want to use cucumber, it should be as simple as "gem
install cucumber", and it should get all the other dependencies. On
my machine it seemed to install treetop, polyglot, and presumably a
few others - but I don't have rsp
Just one comment - I went down this path a bit, and ended up finding
it drastically easier to write a custom formatter.
Take a look at http://wiki.github.com/aslakhellesoy/cucumber/custom-formatters
- or see my post earlier at
http://groups.google.com/group/rspec/browse_thread/thread/c8fde28e5f7577
ter" will build new wiki
pages "tabs" and "foo", and if there is a story page called "foo-1" it will
add the tagged scenarios to it as well. (in a special "qa" section in this
case)
- Korny
On Tue, Apr 14, 2009 at 5:11 PM, Korny Sietsma wrote:
> Go
Good idea. It's at http://gist.github.com/95033
And as I said before, it's pretty hacky :)
- Korny
On Tue, Apr 14, 2009 at 3:11 PM, aslak hellesoy wrote:
>
>
> On Tue, Apr 14, 2009 at 6:06 AM, Korny Sietsma wrote:
>
>> In case anyone followed this: I got everything
p - but I'm happy to share the (messy) code if
anyone is interested.
- Korny
On Wed, Apr 8, 2009 at 4:24 PM, Korny Sietsma wrote:
> Hmm - on digging further, I might be better off writing a custom formatter
> as described at
> http://wiki.github.com/aslakhellesoy/cucumber/custom-format
the wiki, I've
still got some work to do :)
- korny
On Wed, Apr 8, 2009 at 11:01 AM, Korny Sietsma wrote:
> 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
&g
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
I'm a bit confused.
I have a scenario similar to (numbered for clarity):
Scenario: view basic
1) Given I am logged in as 'fred'
2) When I navigate to the 'foo' tab
3) And I select the 'bar' node
4) Then the node 'baz' is displayed
Now, when I have a problem that the 'foo' tab
lakhellesoy-cucumber' - I might actually give up and try again on Monday
when it might all make more sense!)
- Korny
On Fri, Mar 13, 2009 at 5:55 PM, Korny Sietsma wrote:
> I'm a bit confused.
> I have a scenario similar to (numbered for clarity):
> Scenario: view basic
>
I met a great analogy the other day - applies to TDD as well as BDD really.
Unit testing is like double-entry book-keeping.
It takes longer to do the initial work, and yes you have some
repetition - but the reduction in errors saves you time and money
overall.
I'm struggling to think of a projec
e actually run by
an at_exit handler - it took me quite a lot of digging to work out
what *actually* kicked off the stories!
- Korny
On Wed, Apr 16, 2008 at 5:17 PM, Korny Sietsma <[EMAIL PROTECTED]> wrote:
> Sweet! We're on an r&d project, so we'll probably move to edge...
Sweet! We're on an r&d project, so we'll probably move to edge...
- Korny
On Wed, Apr 16, 2008 at 3:53 PM, Ben Mabey <[EMAIL PROTECTED]> wrote:
>
> Korny Sietsma wrote:
> > Hi folks - I'm trying to build a rake task to run our plain-text
> > sto
Hi folks - I'm trying to build a rake task to run our plain-text
stories, both from a normal build and from our continuous integration
server.
However, I'm having a problem - running all.rb doesn't return any sort
of success/failure - so a broken story doesn't indicate to Cruise
Control that the b
Wow - both funny and a little tragic.
He really doesn't understand what "readable" means, does he?
"you keep using that word - I do not think it means what you think it means"
- Korny
On Wed, Mar 5, 2008 at 3:51 AM, Matthias Hennemeyer <
[EMAIL PROTECTED]> wrote:
> Hey all,
> you HAVE to read t
Totally agree with this - I'm happy to work with specs that just define a
single bit of the system's behaviour (i.e. "unit tests") and specs that
define behaviour across several different parts of the system (i.e.
"integration tests") - but it drives me mad when they are all mixed in
together, rath
Hi folks.
I'm trying to work out how to verify that a controller has called a
render:update block similar to:
render :update do |page|
page.replace_html 'edit', :partial => 'form', :locals => { :operation
=> 'edit', :submit_button_value => 'Update' }
end
We used to test this with so
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
23 matches
Mail list logo
