Gathering detailed insights and metrics for gulp-mocha-tdd
Installations
npm install gulp-mocha-tddDeveloper Guide
BETA
Typescript
No
Module System
N/A
Node Version
4.2.4
NPM Version
2.14.12
Releases
26
Contributors
2
Unable to fetch Contributors
Languages
1
JavaScript
JavaScript (100%)
validate.email 🚀
Verify real, reachable, and deliverable emails with instant MX records, SMTP checks, and disposable email detection.
Developer
jhudson8
Download Statistics
Total Downloads
24,584
Last Day
3
Last Week
20
Last Month
36
Last Year
826
GitHub Statistics
MIT License
3 Stars
83 Commits
2 Forks
2 Watchers
2 Branches
2 Contributors
Updated on Oct 31, 2016
Bundle Size
1.04 MB
Minified
296.96 kB
Minified + Gzipped
Maintainers
1
Package Meta Information
Latest Version
2.0.6
Package Id
gulp-mocha-tdd@2.0.6
Size
9.45 kB
NPM Version
2.14.12
Node Version
4.2.4
Total Downloads
Cumulative downloads
Total Downloads
24,584
Last Day
200%
3
Compared to previous day
Last Week
566.7%
20
Compared to previous week
Last Month
-73.7%
36
Compared to previous month
Last Year
-26.2%
826
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
gulp-mocha-tdd
easy test driven development with gulp and mocha
- it('should use mocha for unit tests')
- it('should auto-generate the boilerplate module test describe statement')
- it('should be able to work with your test naming conventions')
- it('should make test driven development easy and convienant')
- it('should support mocha options like breakpoints and grep')
- it('should use conventions to associate modules with unit tests')
- it('should support additional gulp stream handlers (like JSX)')
- it('should re-run module tests when either the module or unit test code changes')
- it('should provide coverage reports')
Usage / Common Examples
Run all tests
> gulp test
Run some tests identified by a grep statement
> gulp test --grep foo
Watch for module or unit test changes
> gulp test-watch
Stop on any debugger statements
> gulp test -d (or --debug-brk)
> node-inspector {in another window}
browse to http://127.0.0.1:8080/debug?port=5858
Test Modules
Test modules do not need the top level describe function (it will be created automatically based on file structure). You can either just have your tests directly in the file (no usage of module.exports) or you can export a function callback that contains your tests. This callback accepts 2 parameters (targetModule, targetModuleDirectoryPath). For example:
var targetModule = require('path/to/target/module');
it('should ...', function() {
expect(targetModule...).to...
});
or
module.exports = function(targetModule, targetBase) {
it('should ...', function() {
expect(targetModule...).to...
});
it('should ...', function() {
expect(require(targetBase + '/targetModuleName')...).to...
});
}
All modules must be within a root directory ("js" by default) and tests can either be in a separate root directory ("tests" by default) or tests can be in a directory relative ("_tests" by default) to the module. Tests can use any naming pattern ("{module name}-test.js" by default).
For example
|-- js
|-- _tests
|-- foo-test.js
|-- foo.js
or
|-- lib
|-- foo.js
|-- tests
|-- foo.spec.js
See Options below for available configuration
Any files within the test directories prefixed with _ will be ignored for testing allowing for utility modules.
Additional Transformations
The pipe option (array of gulp stream handlers) can be used to perform additional transformations. The
following gulpfile can be used to support React JSX
var gulp = require('gulp');
var react = require('gulp-react');
var gulpMochaTDD = require('gulp-mocha-tdd');
gulpMochaTDD(gulp, {
pipe: [react({ harmony: true })]
});
Options
- taskName: the gulp task name ("test" if undefined)
- pipe: array of gulp stream handlers (See above for example)
- init: init function executed once before the tests
- scriptsDirName: top level directory ("js" if undefined)
- testFilePattern: unit test file name (without ext) pattern (use "{name}" to reference the module name; "{name}-test" if undefined)
- testsDirName: name of directory which contains the unit test files ("_tests" if undefined)
- rootTestsDir: true if using a root tests directory and undefined/false if tests are in a directory relative to the module (see examples)
- istanbul: istanbul options which, if included, will include istanbul coverage reports see available options
Installation
Install dependencies
npm install --save-dev mocha
npm install --save-dev gulp
npm install --save-dev gulp-mocha-tdd
Inject the test task in gulpfile.js
var gulp = require('gulp');
var gulpMochaTDD = require('gulp-mocha-tdd');
gulpMochaTDD(gulp, {
// add options here
});
Add .test to your .gitignore file
Coverage Reports
See Options section above for details but here is a quick example to include coverage reports in your tests
var gulp = require('gulp');
var gulpMochaTDD = require('gulp-mocha-tdd');
gulpMochaTDD(gulp, {
istanbul: {
dir: './coverage',
reporters: [ 'lcov', 'text' ],
reportOpts: { dir: './coverage' }
}
});
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
Found 1/29 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 3 are checked with a SAST tool
Score
3
/10
Last Scanned on 2025-03-10
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More