76ca5ef6d4
By deferring the evaluation of these messages, we can avoid the
expensive creation of them when in the majority use case (tests are
passing) they are not needed.
These failure messages were causing performance problems with larger
objects needed to be pretty printed as discussed in #520 and brought up
by @rdy.
[fixes #65925900][fixes #520]
38 lines
1006 B
JavaScript
38 lines
1006 B
JavaScript
describe("toBeNaN", function() {
|
|
it("passes for NaN with a custom .not fail", function() {
|
|
var matcher = j$.matchers.toBeNaN(),
|
|
result;
|
|
|
|
result = matcher.compare(Number.NaN);
|
|
expect(result.pass).toBe(true);
|
|
expect(result.message).toEqual("Expected actual not to be NaN.");
|
|
});
|
|
|
|
it("fails for anything not a NaN", function() {
|
|
var matcher = j$.matchers.toBeNaN(),
|
|
result;
|
|
|
|
result = matcher.compare(1);
|
|
expect(result.pass).toBe(false);
|
|
|
|
result = matcher.compare(null);
|
|
expect(result.pass).toBe(false);
|
|
|
|
result = matcher.compare(void 0);
|
|
expect(result.pass).toBe(false);
|
|
|
|
result = matcher.compare('');
|
|
expect(result.pass).toBe(false);
|
|
|
|
result = matcher.compare(Number.POSITIVE_INFINITY);
|
|
expect(result.pass).toBe(false);
|
|
});
|
|
|
|
it("has a custom message on failure", function() {
|
|
var matcher = j$.matchers.toBeNaN(),
|
|
result = matcher.compare(0);
|
|
|
|
expect(result.message()).toEqual("Expected 0 to be NaN.");
|
|
});
|
|
});
|