01:12
AtariHomestar joined
05:03
raldred_away joined
08:54
petercoulton joined
09:25
petercoulton joined
09:41
<trejs>
can you make webrat handle cookies somehow? (we have a locale cookie that is not set when webrat makes the request)
10:06
technicalpickles joined
12:25
bcardarella_ joined
12:26
<mikepence>
hey wassup
12:26
<mikepence>
so I am at That Moment
12:26
<mikepence>
the moment when I finally learn to use Cucumber
12:26
<mikepence>
any recommended first steps?
12:26
<mikepence>
and can I still use Shoulda?
12:29
<mikepence>
why yes, self, you can probably still use Shoulda
12:29
<mikepence>
also, you should not count on IRC for help. IRC is so pre-Twitter
13:06
<mabes>
mikepence: yes, shoulda is fine the wiki is a good place to start. I'd also recommend the railscasts for getting the basic mechanics of cucumber. for more of a process and philosophy starting point I'd recommend the MWRC presentation
13:07
<mikepence>
excellent
13:19
<tomoj>
how would you test sorting/pagination/etc in cucumber?
13:19
<tomoj>
well I guess I can see how to do pagination
13:20
<tomoj>
but the view matchers we've got don't seem to support checking for stuff in a specific order
13:21
<randy_h>
Tomoj: I would probably spec the sort order on the controller in Rspec instead of in Cuke.
13:22
<randy_h>
Or you could write a step that just looked into the response and expect unique-stringA.*unique-stringB.*unique-stringC.*, where these unique strings were a displayed part of the records you added in the Givens.
13:22
<randy_h>
IOW, a simple regex could prove the desired ordering.
13:22
<tomoj>
or I think nth-child could work too
13:23
<randy_h>
good point.
13:27
<tomoj>
regex would probably be simpler
13:28
<randy_h>
Yeah. Seems to me, whatever gets you to the next Green faster. Cuz it's now about how good your cuke code is, it's about how well your software is delivering value to your customer.
13:28
<randy_h>
*not about how good...
14:12
technicalpickles joined
15:57
<petelacey>
Hate to interrupt, but I can't find this answer anywhere. How do you pend an entire scenario? Or at least just comment it out. Scenario mind you, not step.
15:59
<Lenary>
you could tag it then tell it to do all but that tagged one
15:59
<Lenary>
don't hold me to that though
16:00
<* petelacey>
is looking up tags
16:03
<petelacey>
Thanks, Lenary, that looks like it'd work. Seems that there should be a more, erm, natural way to do it, though.
16:03
<Lenary>
just tag lots of things @pending
16:03
<Lenary>
then exclude that
16:03
<Lenary>
self-documenting
16:19
<atmos>
anyone know how to test autocompleters in safariwatir ?
16:20
<* atmos>
has the cucumber part down, just unsure of how to do keydown events
16:22
technicalpickles joined
16:45
technicalpickles joined
17:01
<petelacey>
BTW, Lenary, the tag tricked worked like a champ. Thanks again.
17:08
technicalpickles joined
19:59
AtariHomestar joined
20:02
AtariHomestar joined
20:36
<jamescarr>
how can I do something before running all/any cucumber features?
20:37
<jamescarr>
for example, I am using couchdb with my application
20:37
<jamescarr>
I would like to clear couchdb before an tests run
20:41
<tomoj>
jamescarr: if you want to do something once before all tests run, you can just put it in your env.rb
20:41
<tomoj>
before each each scenario, you can pass a block to Before in env.rb
20:47
<jamescarr>
thanks... i thought it was in env.rb
20:51
<jamescarr>
maybe it's better to just mock out the source of data for the model?
20:56
<tomoj>
usually you use cucumber to test everything
20:56
<tomoj>
including interaction with the database
21:47
technicalpickles joined
22:36
AtariHomestar joined