Add a matcher for `x === undefined || x === null` and/or `x !== undefined || x !== null` about jasmine HOT 2 OPEN

toBeDefined is an unfortunate relic of the very early (pre-1.3) days, when there was no .not and the only way to negate a matcher was to write a second one that did the opposite. All the other negated matchers were removed in 2.0, with only the toBeDefined/toBeUndefined pair retained. I think that if there was no toBeDefined and you'd had to write .not.toBeUndefined() instead, you probably wouldn't have been surprised by its behavior.

I think the proposed matcher is relatively niche. Normally I'd reach for a more specific assertion like toEqual(someExpectedValue), toEqual(jasmine.any(String)), or even toBeTruthy(). But I can see how it would be useful in some cases, and there's precedent in jasmine.anything(), so I don't mind having it as long as it's not going to confuse people.

The toBeAnything name is consistent with jasmine.anything, but I think it's vague enough to cause the same kind of problem that you ran into with toBeDefined. What about something like toBeNullOrUndefined? So in the normal case where you want to assert that you got some sort of non-nothing value back, you'd write expect(something).not.toBeNullOrUndefined(). A bit more verbose, but I think the explicitness is good in this case.

from jasmine.