Unit testing of widgets? about fortitude HOT 6 CLOSED

What do the contents of that widget look like?

I just tried what you mentioned on one of my simpler widgets and it works fine:

irb(main):020:0> Views::Widgets::Base.new.to_html
=> "<!-- BEGIN Views::Widgets::Base depth 0: :id => (DEFAULT) nil, :element => (DEFAULT) nil, :classes => (DEFAULT) nil -->\n<div id=\"u9iydhwl\" class=\"\">\n</div>\n<!-- END Views::Widgets::Base depth 0 -->"

from fortitude.

from fortitude.

@karlhe, take a look at this Gist that I wrote up and attached the relevant files' contents to, as well as the error dump that prompted filing of this issue.

Note the update at the bottom of the intro, where I document discovery of a workaround that indeed allows me to unit test widgets that yield to blocks if specified — by wrapping the widget of interest in a dummy widget. Ceremonious overkill? Absolutely. Can I think of a better way to do it, that actually works? Nope.

from fortitude.

Hey, @alexch, how's life? Your questions should be answered by that Gist I linked to in my answer to @karlhe.

from fortitude.

I'm reopening this, at least temporarily. It strikes me that Fortitude might be breaking #block_given? in a widget context, and that would be bad. At minimum, I want to write some specs around this to make sure it's completely solid (and stays that way). I'll also make sure there aren't some weird situations in which MyWidget.new.to_html doesn't work for some reason. I very much want Fortitude widget testing to Just Work. :)

from fortitude.

There was, in fact, an issue here underneath: #block_given? always returned true inside a Fortitude widget's content method, whether or not there was any block passed anywhere. Fixed now.

from fortitude.