I'm a little confused about what you're seeing here. Can you gist the
.feature file containing the special character? Features are parsed as
UTF-8, so multibyte characters in that encoding should be fine.
Mike
> Thanks for any help!
> Andrew
>
> --
> You received this message because you are subscribed to the Google Groups "Cukes" group.
> To post to this group, send email to cu...@googlegroups.com.
> To unsubscribe from this group, send email to cukes+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/cukes?hl=en.
>
>
It'll be easier to see what you're doing if you gist or post your
feature (or a similar example) someplace, but from what you've
described it sounds like you're putting the escape codes into the
feature file itself. Cucumber passes the content of the tables
straight to the test code, so try copying in the literal character
rather than an escaped representation of it, i.e. use ™ in the feature
rather than ™.
Mike
Thanks for posting these! From the looks of the error message from
Capybara, I think you are including single quotes around the item that
you're searching for. That should be unnecessary, unless those single
quotes are in the HTML itself. You can take a look at this gist to see
what I would expect to see in that table:
https://gist.github.com/791595.
If you have tried that and still are having no luck, maybe the page
itself doesn't contain what you expect it to. The cucumber-rails steps
contain a step "Then show me the page" which will open up the current
page that Cucumber is visiting in a browser. (I think you'll need to
install the launchy gem for it to work.)
Also, if you're interested, you might want to check out these links
about writing Cucumber scenarios:
* http://benmabey.com/2008/05/19/imperative-vs-declarative-scenarios-in-user-stories.html
* http://cuke4ninja.com/chp_feature_files.html
I notice that you're using a very low-level and imperative style. This
has it's place, but you might find you end up writing clearer
scenarios (and with a more maintainable suite of features), if you
focus on expressing things at a slightly higher level.
Mike