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
Unlike business app authors, component library authors often need to make assertions on the actual layout a component and how it renders. One way to deal with this is to add custom filters, like clientTop if you need to make an assertion on what the coordinates of the top, you can add a filter.
awaitcomponent.has(clientTop: 10);
But a filter that nobody should ever use except in the context of the component library itself is of dubious value.
One option is to make element a filter, that way, you can implement custom matchers on it to your heart's content. So instead of having a clientTop filter, you can just have a matcher:
awaitcomponent.has(element: withClientTop(10));
The text was updated successfully, but these errors were encountered:
Unlike business app authors, component library authors often need to make assertions on the actual layout a component and how it renders. One way to deal with this is to add custom filters, like
clientTop
if you need to make an assertion on what the coordinates of the top, you can add a filter.But a filter that nobody should ever use except in the context of the component library itself is of dubious value.
One option is to make
element
a filter, that way, you can implement custom matchers on it to your heart's content. So instead of having aclientTop
filter, you can just have a matcher:The text was updated successfully, but these errors were encountered: