You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discussed in slack and @sglanzer agrees, the components should be getting hooks set on them. I'm opening an issue to that effect right now.
While the consumer probably doesn't care about some of the hooks, the component itself might care. For instance, if the frost-icon needs to be wrapped by a <div> with a particular class set on it, this component's tests should be able to grab that <div> with a hook.
Right now, we are getting a hook set on icon:
ember-frost-info-bar/addon/templates/components/frost-info-bar.hbs
Line 3 in 21648cd
Does this provide the value we want?
Would a tester rather be setting a hook on the icon component
ember-frost-info-bar/addon/templates/components/frost-info-bar.hbs
Line 4 in 21648cd
<svg>
.The text was updated successfully, but these errors were encountered: