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

console-fail-test is meant to support any (test framework) & (spy library) combination. It will auto-detect your combination if possible and use the most appropriate environment hooks and function spies it can find.

In general, you can use the Node API to request specific test frameworks and spy libraries:

require("console-fail-test").cft({
    testFramework: "jest",
    spyLibrary: "jasmine",
});

Test frameworks that are ✨ auto-detectable can be supported by just running console-fail-test/setup.js before tests. For others, use the Node API with their API request:

require("console-fail-test").cft({
    testFramework: require("ava"),
});

See open test framework support issues for progress!

If a supported spy library isn't detected, an internal fallback will be used to spy on console methods.

You can request a specific test library using the Node API with its API request:

require("console-fail-test").cft({
    spyLibrary: "sinon",
});

By default, console-fail-test will error on any called console method. If you'd like allow certain methods, pass a console object to the cft API when you set it up:

require("console-fail-test").cft({
    console: {
        warn: true, // won't error on any instance of console.warn
    },
});

Logging to the console during tests can be a sign of

• 🚫 warnings from third-party libraries such as React for improper usage
• 🤕 temporary code that shouldn't be checked into your project
• 📢 unnecessary spam in your tests window

This little library throws an error after each test if a console method was called during it. It's got some nifty features:

• 📊 Summary of which methods are called with calling arguments
• 🛫 Failures are thrown after tests finish, so your tests will fail normally if they should

Look how fancy the terminal output is with Jest!

Requires:

• Node.js >10 (LTS)
• Yarn

After forking the repo from GitHub:

git clone https://github.com/<your-name-here>/console-fail-test
cd console-fail-test
yarn
yarn run verify

yarn run verify will run a full build and set up the package to be consumed locally.

We'd love to have you contribute! Check the issue tracker for issues labeled accepting prs to find bug fixes and feature requests the community can work on. If this is your first time working with this code, the good first issue label indicates good introductory issues.

Please note that this project is released with a Contributor Covenant. By participating in this project you agree to abide by its terms. See CODE_OF_CONDUCT.md.