Added tests and expectations for NaN. Ex: expect(4).not.to.be.NaN;

[bradcypert]

Added support for NaN as per @keithamus comment on issue #477

I agree. I think the to.be.NaN; structure is what makes the most sense for this issue.

[keithamus]

Great work @bradcypert! Couple of notes:

• Please don't compile chai.js, this is done per release. Could you please rebase and exclude the chai.js changes?
• Could you please also add assert.isNaN and assert.isNotNaN - these are also important functions to be included.
• Documentation is missing from this. Please refer to other addProperty calls, to see how we document chai properties.
• Please also add tests for .should.be.NaN and so on, and tests for assert.is[Not]NaN - eventually I'll be adding coverage checking back into chai, and it'd be nice to make sure things are all properly covered 😜

Fix the above issues, and I'll be overjoyed to hit the big green merge button 😄

[bradcypert]

I've done everything excluding the rebase, however, my assert tests are failing against saucelabs, but running locally.

Any chance you'd be interested in taking a look?

[keithamus]

Passing on travis, which is good enough for me 😉

[bradcypert]

Haha, fair enough. My git-fu is weak. How do I go about rebaseing to prevent my changes to chai.js?

[keithamus]

I don't have much time right now - but could help out maybe tomorrow.

In the meantime you could read a tutorial, e.g. https://www.atlassian.com/git/tutorials/rewriting-history/git-rebase. You just need to squash both commits and checkout the old copy of chai.js and then amend the commit with the older checked out copy.

[bradcypert]

Squashed everything and reverted my incidental change to Chai.js

[keithamus]

Great work @bradcypert 😸

[screendriver]

to.be.NaN; should be added to the docs 😉

[keithamus]

@screendriver it will be soon. The docs are pretty badly out of date but we're working on them 😄

[screendriver]

👍