to satisfy: Improve diffs and support asserting textContent.

[papandreou]

No description provided.

[papandreou]

The Travis failure seems bogus, any idea @Munter?

[Munter]

Looks like just a temporary glitch. Rerunning it worked

[Munter]

The changes look great. Thanks!

[Munter]

Published in 1.3.0

[sunesimonsen]

@Munter awesome, this plugin is tremendously useful. It is the first time I'm using it.

[sunesimonsen]

@Munter I was trying to achieve this: https://github.com/One-com/knockout.autocomplete/blob/master/test/knockout.autocomplete.spec.js#L37-L63 and ran into a very weird diff :-)

[Munter]

Seeing deep structures like that makes me want to enable html syntax in the comparison, like what @bruderstein is doing in https://github.com/bruderstein/unexpected-react-shallow

Unfortunately not as easy in actual dom versus virtual dom

[sunesimonsen]

@Munter I don't exactly understand what you mean, the html is syntax highlighted in the diff.

[Munter]

expect(node, 'to render as', '<div class="foo">bar</div>');

[sunesimonsen]

@Munter is it <div class="foo">bar</div> you want highlighted?

[sunesimonsen]

That assertion makes sense, it should parse the rhs as html and copy the lhs, trim and remove all empty text nodes and use to equal. Then I guess you'll get a nice diff.

[sunesimonsen]

@Munter sorry I completely misunderstood you - you want jsx in you your tests, with highlighting in you editor right?

[Munter]

Jsx, maybe. Html as a string might also be more readable. Means having to learn less of the specific syntax for the assertion

[sunesimonsen]

Maybe the new strings in es6 would work in combination with an editor extension:

expect(node, 'to render as', html`<div class="foo">bar</div>`);