01:39
<giorgian>
hi. I'm trying cucumber for the first time on an exitisting rails app; when I do rake cucumber:all it tries to invoke "rake db:schema:load", which, in my case, fails (I'm using some mysql specific stuff which doesn't get translated correctly in schema.rb). How do I tell cucumber to do db:migrate, instead?
01:41
<ariejan>
Hey. With tablish, how can I leave out an entire column before diffing it?
02:20
ashley_moran joined
03:20
jschoolcraft joined
05:27
<ashley_moran>
Hi all, been working on getting features into cucumber-rails in prep for working on rails 3 compatability
05:28
<ashley_moran>
very little there but it's a start, hopefully get decent coverage this avvy
07:26
<mattwynne>
nice one ashley_moran
07:27
<ashley_moran>
hi mattwynne - slow going as i had to get a harness in place first, but i've had a coffee now :)
07:27
<ashley_moran>
i'm getting strange behaviour from the generator though... doesn't appear to be running erb on cucumber.yml?
07:28
<ashley_moran>
that's the latest gem in a rails 2.3.5 app
07:29
<ashley_moran>
mattwynne: no it's not, ignore me
07:53
<ashley_moran>
anyone know what "rerun.txt" is in the context of a generatorL
07:56
<ashley_moran>
is cucumber.yml supposed to be an erb file these days? that threw me
07:57
<ashley_moran>
or is the generated cucumber.yml actually a yaml file? i've never seen one with embedded ruby like that
08:30
<kevwil>
what's the best way to use Cucumber with REST-only APIs?
08:31
<kevwil>
I'm trying to hack something together with rest-client and custom steps, but it's funky.
08:46
<mrkurt>
kevwil: I haven't done it much, but we just treat them like normal web pages
08:46
<mrkurt>
and have helper forms we can submit to them
08:48
<kevwil>
mrkurt: if you didn't have helper forms, could you work with all the http verbs, or is that the only way to POST / PUT / DELETE?
08:48
<mrkurt>
I think you can write custom steps to handle that pretty easily
08:49
<kevwil>
mrkurt: that's what I'm trying to do now
08:50
<kevwil>
it seems webrat is very popular, but that seems very HTML specific
08:50
<mrkurt>
it seems like a rest api might be a better candidate for regular functional tests, tbh
08:50
<kevwil>
looking for a better shortcut to REST testing
08:51
<kevwil>
mrkurt: why?
08:51
<mrkurt>
because it's an API and not a user facing thing
08:51
<mrkurt>
you're not writing stories as a "user"
08:51
<kevwil>
the draw of cucumber is the language, the use case dialog that all parties can understand, but when the product is a REST api ....
08:51
<mrkurt>
I don't think all parties necessarily understand the use case of a REST api
08:52
<mrkurt>
a sample client app that uses the rest api? s ure
08:52
<kevwil>
here they do
08:52
<kevwil>
that's what we do
08:52
<mrkurt>
then test that client app :p
08:52
<mrkurt>
with cucumber!
08:52
<kevwil>
no, no client apps, the API is the product
08:53
<mrkurt>
right, what I'm saying is, cucumber would be an obvious fit to run against a sample app that uses your rest api
08:53
<mrkurt>
but low level testing of the api itself isn't what I'd use integration testing for
08:53
<kevwil>
sure, obviously
08:53
<mrkurt>
I'd use rspec
08:54
<mrkurt>
or similar
08:54
<kevwil>
if I didn't want to communicate with the business people, I'd do the same thing
08:54
<mrkurt>
I understand that not everyone would be able to read those tests quite as easily, but I can't fathom how cucumber features are going to be written that make that a whole ton better
08:54
<kevwil>
the draw is the common language
08:54
<mrkurt>
do you have a sample feature?
08:55
<mrkurt>
who's perspective is it written from?
08:55
<kevwil>
I'd have to sanitize one
08:55
<kevwil>
written from the perspective of the API user
08:56
<kevwil>
could be an internal customer, a client, or a client's client
08:56
<mrkurt>
well, you don't really need to convince me either way if it works for you
08:57
<mrkurt>
but I think you're stuck with a whole ton of custom steps to map whatever client lib you want to use to features
08:57
<kevwil>
I guess my expectation that advanced Ruby testing frameworks would be up to the current market of customer-facing API products is a bit ahead of its time
08:57
<mrkurt>
if you're returning html, webrat will work ok
08:57
<mrkurt>
well, your customer's going to use an API as an API
08:57
<mrkurt>
which matches, say, rspec much better than it matches cucumber
08:58
<kevwil>
yeah, we're considering returning html for the QA department, but I'm trying to get cucumber to bridge all those gaps with common language
08:59
<kevwil>
mrkurt: time for our morning stand-up meeting, thanks for thinking this through with me
10:26
<ashley_moran>
i'm back... some more progress on the rails 3 cucumber-rails generator
10:27
<ashley_moran>
now have a feature file makes a walking skeleton of the skeleton generator and builds a few apps
10:29
<ashley_moran>
off out now to the sheffield rug now
12:04
chriseppstein joined
13:54
<kunalksm>
I am integrating selenium with webrat in my cucumber stories. I have to perform one step in selenium and rest steps in the scenario does not require client side testing. Is it possible to switch between webrat and selenium in a scenario ?
13:54
<kunalksm>
I understand this is more of webrat question .. but i thought somebody might know about this in this group
14:26
<phinze>
kunalksm: not really, as they're totally different strategies for testing a webapp
14:26
<phinze>
but you should really be using webrat's selenium integration
14:27
<phinze>
so you really are using webrat the whole time
14:27
<phinze>
which then in the background talks to selenium,
14:30
<kunalksm>
phinze: Thanks… I am actually trying to do that.. but I was hoping to squeeze more speed by limiting steps to selenium only when they cannot be preformed by webrat
14:32
<phinze>
the way we accomplish that is to divide our suite into two
14:32
<phinze>
features that require selenium, features that require nokogiri(break in selenium) and features that work in both
14:32
<phinze>
(so three i guess ;) )
14:33
<phinze>
i based that structure off an article i think, let me see if i can't find it
14:51
<phinze>
did that more or less
14:51
<phinze>
that way most of tests can be run with webrat
14:51
<phinze>
and selenium necessary tests can stay w/ selenium
14:52
<phinze>
kunalksm: ^^
16:49
<BBHoss>
whats the status with Rails 3 and Cucumber, what needs to be fixed?
16:57
<odigity>
rails noob with a cucumber install question
16:57
<odigity>
I installed the gem, but it didn't add any rake tasks
16:57
<odigity>
yet the screencasts I've seen start by running 'rake cucumber' to generate the features/ subdir and other starting files
16:58
<odigity>
ah, sorry, I don't mean rake, I mean script/generate
16:58
<odigity>
the screencasts start with "script/generate cucumber", but installing the cucumber gem didn't add any generators
17:06
<odigity>
did my last five messages go through? just noticed I wasn't registered with the nickserv
20:24
<donaldball>
Hey, is anyone using any nifty tools to help the stakeholders visualize and browse the coverage of their cucumber scenarios?
20:38
aslakhellesoy joined
20:50
aslakhellesoy joined
22:59
chriseppstein joined
23:18
<tanvir>
i am in a problem
23:18
<tanvir>
anybody there to help?
23:23
<tanvir>
i need help :(