`toContainMatchingElement` considers `className` prop rather than actual HTML about enzyme-matchers HOT 6 CLOSED

Thanks, nice to know I'm not alone in this! Filed enzymejs/enzyme#2560 for it.

from enzyme-matchers.

That's expected - el DOES contain <MyElement className='foobar' />.

Try expect(el.hostNodes()).toContainMatchingElement('.foobar');.

from enzyme-matchers.

Upon further investigation, I've realized that this is an enzyme problem, not this library. I had initially misread a test that made me incorrectly think the problem was isolated to this library. Sorry for the mistaken report!

from enzyme-matchers.

@iangreenleaf i assume it's an enzyme usage problem, as i've indicated? if not, please file an issue on enzyme.

from enzyme-matchers.

@ljharb your hostNodes() suggestion didn't work because it doesn't seem to return the single element (it shows up as an empty set). But I was able to get a correct test by using a similar strategy of calling render() and Cheerio functions to parse the actual HTML.

I suspect I would get told the same thing by enzyme, that this is working as expected. I personally think it's pretty wild that enzyme would match a CSS selector for a class name that is not being rendered, but maybe I'm just a curmudgeon.

from enzyme-matchers.

No, I agree with you - the issue is likely that selectors match the components themselves as well as the things they render.

render() should generally be avoided and rarely needed, and i think mount should work for this case. If you file an issue on enzyme we can try to work out the problem.

from enzyme-matchers.