Documentation site

[sunesimonsen]

• <DOMElement> to have text <any>
• <DOMElement> to [only] have (attribute|attributes) <array|object>
• <DOMElement> to [only] have (attribute|attributes) <string+>
• <DOMElement> not to have (attribute|attributes) <array>
• <DOMElement> not to have (attribute|attributes) <string+>
• <DOMElement> to [exhaustively] satisfy <string>
• <DOMElement> to [exhaustively] satisfy <object>
• <DOMElement> to [exhaustively] satisfy <DOMElement>
• <DOMElement> to have [no] (child|children)
• <DOMElement> to have (class|classes) <array|string>
• <DOMElement> to only have (class|classes) <array|string>
• <DOMDocument|DOMElement|DOMDocumentFragment> to contain [no] elements matching <string>
• <DOMNodeList> to [exhaustively] satisfy <DOMNodeList>
• <DOMDocument|DOMElement|DOMDocumentFragment> [not] to match <string>
• <DOMDocument|DOMElement|DOMDocumentFragment> [when] queried for [first] <string> <assertion?>
• <string> when parsed as HTML <assertion>
• <string> when parsed as XML <assertion>

Stuff that might be covered by the above.

• <DOMTextNode> to [exhaustively] satisfy <DOMElement>
• <DOMElement> to [exhaustively] satisfy <DOMTextNode>
• <DOMDocument> to [exhaustively] satisfy <DOMDocument>
• <DOMDocumentFragment> to [exhaustively] satisfy <object|array>
• <DOMDocumentFragment> to [exhaustively] satisfy <DOMDocumentFragment>
• <DOMTextNode> to [exhaustively] satisfy <DOMTextNode>
• <DOMTextNode> to [exhaustively] satisfy <regexp>
• <DOMDocument> to [exhaustively] satisfy <string>
• <DOMDocumentFragment> to [exhaustively] satisfy <string>
• <DOMTextNode> to [exhaustively] satisfy <object>
• <DOMTextNode> to [exhaustively] satisfy <any>

This is too weird:

• <DOMNodeList> to [exhaustively] satisfy <string>

[coveralls]

Coverage decreased (-0.8%) to 93.211% when pulling 75d078b on ssimonsen/documentation-site into 10b22a0 on master.

[coveralls]

Coverage increased (+0.7%) to 94.737% when pulling 571b73e on ssimonsen/documentation-site into 2fc89c3 on master.

[sunesimonsen]

Prepublished here https://munter.github.io/unexpected-dom/

[sunesimonsen]

@papandreou don't know what is up with Coveralls, I would expect the coverage to go up.

[papandreou]

Istanbul seems to agree with coveralls.

Before (master, 31d8e83)

=============================== Coverage summary ===============================
Statements   : 94.03% ( 504/536 )
Branches     : 85.5% ( 283/331 )
Functions    : 95.62% ( 131/137 )
Lines        : 94.03% ( 504/536 )
================================================================================

After (ssimonsen/documentation-site, 2113973)

=============================== Coverage summary ===============================
Statements   : 93.62% ( 514/549 )
Branches     : 84.89% ( 281/331 )
Functions    : 96.43% ( 135/140 )
Lines        : 93.62% ( 514/549 )
================================================================================

And roughly the same after rebasing ssimonsen/documentation-site on master:

=============================== Coverage summary ===============================
Statements   : 93.66% ( 517/552 )
Branches     : 84.98% ( 283/333 )
Functions    : 96.43% ( 135/140 )
Lines        : 93.66% ( 517/552 )
================================================================================

Comparing the two coverage reports, the difference seems to be down to the introduction of <DOMElement> to [exhaustively] satisfy <regexp>, which doesn't get any coverage, and the fact that the jsdom-based parsing doesn't get coverage anymore (before on the left):

The reason is that bootstrap-unexpected-markdown.js now sets up a document global, and it's being unconditionally included when running the test suite, not just the documentation tests: https://github.com/Munter/unexpected-dom/blob/2113973bc4e311d5b98f6233974b155e28dafa25/test/mocha.opts#L2

[papandreou]

Hey, this looks great! 🚢

I found a few typos, PR here: #207

When reading through the docs was a little unsure about the createElement function, which might be mistaken for a built-in function because it's not explicitly defined on the doc site. On the other hand, the function itself isn't really the point, and it's perfectly understandable what it does, so it's probably not worth spending too many words on explaining it :)

[sunesimonsen]

Thanks for the explanation, let me create a test for the new addition. About the creareElement function, let's see if people gets confused about it.