Brian Vaughn b5334a44e9 toWarnInDev matcher; throw on unexpected console.error (#11786) ... * Added toWarnInDev matcher and connected to 1 test * Added .toLowPriorityWarnDev() matcher * Reply Jest spy with custom spy. Unregister spy after toWarnDev() so unexpected console.error/warn calls will fail tests. * console warn/error throws immediately in tests by default (if not spied on) * Pass-thru console message before erroring to make it easier to identify * More robustly handle unexpected warnings within try/catch * Error message includes remaining expected warnings in addition to unexpected warning		2018-01-02 11:06:41 -08:00
..
matchers	toWarnInDev matcher; throw on unexpected console.error (#11786)	2018-01-02 11:06:41 -08:00
spec-equivalence-reporter	toWarnInDev matcher; throw on unexpected console.error (#11786)	2018-01-02 11:06:41 -08:00
typescript	toWarnInDev matcher; throw on unexpected console.error (#11786)	2018-01-02 11:06:41 -08:00
config.build.js	Run 90% of tests on compiled bundles (both development and production) (#11633)	2017-11-23 17:44:58 +00:00
config.source.js	Forbid Haste in Jest (#11647)	2017-11-23 18:02:47 +00:00
noHaste.js	Forbid Haste in Jest (#11647)	2017-11-23 18:02:47 +00:00
preprocessor.js	use different eslint config for es6 and es5 (#11794)	2017-12-11 15:52:46 +00:00
setupEnvironment.js	Run some tests in Node environment (#11948)	2018-01-02 18:42:18 +00:00
setupTests.js	toWarnInDev matcher; throw on unexpected console.error (#11786)	2018-01-02 11:06:41 -08:00