I use something similar, however as I need to have my database pre
populated with valid user accounts (the dreaded fixtures) I use
something like..
Given the following users are logged in:
|user|
|first|
|second|
|third|
When the first user sends a message to the second us
Ahh no I'm still using 0.2.0
I was going to write up a gist as an example, I actually just stopped
using background and put it in the scenario outline, but I'll try it
on 0.3.0
Thanks
On Apr 27, 5:11 am, Andrew Premdas wrote:
> Is this with 0.3.0? If not this might have been recently fixed as I
Ok there is a different bug with 0.3.0, I'll work up a gist, but it
seems that background with scenario outline now has background run
before the Before hook, or maybe the before hook is not being run. The
docs say background runs after the before hook.
I need to debug further to see what is actu
/gists/102789/download
I am using
cucumber (0.3.1)
jruby 1.1.6
also same results with ruby 1.8.6 (2008-08-11 patchlevel 287) [i686-
linux]
On Apr 27, 2:47 pm, wolfmanjm wrote:
> Ok there is a different bug with 0.3.0, I'll work up a gist, but it
> seems that background with scenario
to_sexp should do it for now, but I'll file a ticket as #name would be
useful.
Thanks
On May 1, 2:51 pm, aslak hellesoy wrote:
> > Hi,
>
> > Given the hook:
>
> > After do |scenario|
>
> > end
>
> > How do I get the name of the scenario from the scenario parameter?
>
> > scenario.name doesn't w
filed the ticket, as it turns out that the name is not available in
the sexp for scenario outlines.
Thanks
On May 1, 4:03 pm, wolfmanjm wrote:
> to_sexp should do it for now, but I'll file a ticket as #name would be
> useful.
>
> Thanks
>
> On May 1, 2:51 pm, aslak hell
Thanks, this is a work in progress it should get more sophisticated as
I write more features.
BTW Aslak this is why I needed the scenario name in the After hook, I
get a lot of Erlang messages which get stored, and the Steps should
test for them and consume them off the queue, however as Erlang an
