We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Given the following structure
project/ Gruntfile.js spec/ someSpec.js
In spec/someSpec.js , I have :
var assert = require("assert"); describe('something', function(){ it('should do stuff', function(){ assert.equal(0, 42); }); });
And my Gruntfile has this config for jasmine_node :
jasmine_node : { test : { options : { forceExit: true, match: '.', matchall: false, extensions: 'js', specNameMatcher: 'spec', }, all : ["spec/"] } }
Tests are never run :
grunt jasmine_node:test Running "jasmine_node:test" (jasmine_node) task util.print: Use console.log instead undefinedutil.print: Use console.log instead Finished in 0.001 secondsutil.print: Use console.log instead util.print: Use console.log instead 0 tests, 0 assertions, 0 failures util.print: Use console.log instead util.print: Use console.log instead Done, without errors.
I'm obviously missing something huge, but I can't figure out what...
The text was updated successfully, but these errors were encountered:
Your test is named "someSpec.js" and your specNameMatcher is "spec". Change the specNameMatcher to "Spec", or change your test to "some_spec.js".
Sorry, something went wrong.
I tried that, but it does not work either.
I'm using OSX and it seems to work regardless of the casing used for specNameMatcher or in the filenames. Using version 0.2.1.
specNameMatcher
0.2.1
@phtrivier, did you ever figure this out? I'm running into the same problem.
No branches or pull requests
Given the following structure
In spec/someSpec.js , I have :
And my Gruntfile has this config for jasmine_node :
Tests are never run :
I'm obviously missing something huge, but I can't figure out what...
The text was updated successfully, but these errors were encountered: