Question 1

Why does my gulp-mocha test suite hang and not exit?

Accepted Answer

This often happens due to open connections or lingering callbacks. The README suggests adding event handlers for 'error' and 'end' to force process exit, or using the 'exit' option in Mocha to handle it automatically.

Question 2

gulp-mocha or running Mocha directly with npm scripts: which is better?

Accepted Answer

gulp-mocha is best if you're already using Gulp for builds and want integrated test runs within your pipeline. For standalone testing without Gulp, direct Mocha with npm scripts is simpler and avoids extra dependencies.

Question 3

How do I add a custom reporter to gulp-mocha?

Accepted Answer

First, install the reporter package via npm, then specify it in the options. For example, after installing 'mocha-lcov-reporter', pass {reporter: 'mocha-lcov-reporter'} to the mocha() function in your Gulp task.

Question 4

Does gulp-mocha support running tests in watch mode?

Accepted Answer

No, gulp-mocha itself doesn't include watch mode. You need to use Gulp's gulp.watch() or other plugins to trigger the mocha task on file changes, adding an extra layer of configuration.

Question 5

How to handle test failures gracefully in gulp-mocha?

Accepted Answer

Attach event listeners to the stream for 'error' and 'end' events. The README provides code examples to log errors and ensure the process exits correctly, preventing silent failures in CI environments.

Question 6

What are common pitfalls when using gulp-mocha?

Accepted Answer

Key issues include forgetting to set {read: false} for file streams, placing plugins before mocha in the pipe, and not handling asynchronous test exits, which can lead to hanging processes or uncaught errors.

gulp-mocha

What is gulp-mocha?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions