53 Commits

Author	SHA1	Message	Date
Gregg Van Hove and Tim Jarratt	7e071547f5	Custom matchers fail to behave as expected ... If they return false, that should be respected. Submitted via @tjgrathwell [Finish #58184156] close #434	2013-10-03 15:13:27 -07:00
Davis W. Frank	0ac497db6b	Simplifying toThrow: ... - It still supports no expected, which means that something was thrown - Expected value is now tested via equality in order to pass Adding toThrowError: - toThrowError() passes if an Error type was thrown - toThrowError(String) & toThrowError(RegExp) compare Expected to the Error message - toThrowError(Error constructor) compares Expected to the constructor of what was thrown - toThrowError(Error constructor, String) & toThrowError(Error constructor, RegExp) compares both the Error and the message Also, equality now handles Errors, enforcing the message as part of the equality.	2013-06-03 09:24:43 -07:00
Davis W. Frank	d53002c63a	Matchers & Matchers specs now broken up into individual files. There is now a requireMatchers jasmineRequire function to attach matchers properly.	2013-06-02 22:22:25 -07:00