console-fail-test/lib/environments/testEnvironmentTypes.cjs.map

Gently fails test runs if the console was used during them. 📢

{"version":3,"sources":["../../src/environments/testEnvironmentTypes.ts"],"sourcesContent":["import { SpyCallArgs } from \"../spies/spyTypes.js\";\nimport { CftRequest } from \"../types.js\";\n\nexport type TestFrameworkSelector = (\n\trequest: CftRequest,\n) => TestFramework | undefined;\n\nexport interface TestFramework {\n\t/**\n\t * Adds a callback to be called after each test.\n\t * @param callback - Called after each test.\n\t */\n\tafterEach: (callback: (hooks?: TestAfterHooks) => void) => void;\n\n\t/**\n\t * Adds a callback to be called after each test.\n\t * @param callback - Called after each test.\n\t */\n\tbeforeEach: (callback: () => void) => void;\n\n\t/**\n\t * Maps each spy method name and calls to the args that should be logged.\n\t * @param call - A method call's args and name.\n\t * @returns The args that should be logged.\n\t * If not provided, the method calls are returned directly.\n\t */\n\tmapSpyCalls?: (call: SpyCallsAndName) => SpyCallArgs[];\n}\n\nexport interface TestAfterHooks {\n\treportComplaint?: (complaint: TestComplaint) => void;\n}\n\nexport interface SpyCallsAndName {\n\tmethodCalls: SpyCallArgs[];\n\tmethodName: string;\n}\n\n/**\n * It is preferred for test frameworks to directly throw `error`, as it contains a friendly call stack.\n * However, if the test framework doesn't format multiline error messages well, it might instead\n * log a separate failure for each of the `methodComplaints`.\n */\nexport interface TestComplaint {\n\terror: Error;\n\tmethodComplaints: SpyCallsAndName[];\n}\n"],"mappings":";;;;;;;;;;;;;;AAAA;AAAA;","names":[]}