Remove dependency on jasmine.json file when running tests

[jasmine]

Remove dependency on jasmine.json file when running tests

[amavisca]

You can filter individual tests with the jasmine --filter="some string"or specify a file name with jasmine path/to/spec/file.js.

There are some docs here:
http://jasmine.github.io/edge/node.html#section-Running_tests

You can also use fit and fdescribe to focus within your code:
http://jasmine.github.io/edge/focused_specs.html

Feel free to close this if these solved your issue!

[indigo0086]

I think there is a misunderstanding. The problem is that the command requires a variable set to point to a jasmine.json file which I feel for most cases is redundant. I'd prefer a solution as simple as jasmine path/to/spec/**/*.spec.js

[amavisca]

@indigo0086
Yep, you're right. We started by adding these features in one by one and originally depended on having that json file around. As we've added more CLI options it seems like we're at the point where that file can be optional. I'd be happy to look at a PR that does that.

[jasonkarns]

Probably as a separate issue, but I would have much preferred to see a jasmine property in package.json that contained all the jasmine-specific config, rather than Yet Another Config File™

[slackersoft]

@jasonkarns That sounds reasonable as well. As @amavisca mentioned some of this grew a bit organically based on how we had configured some of the other Jasmine repositories. We would be happy to review a pull request that allows Jasmine to read its config from the including project's package.json file. For now it should leave the jasmine.json file parsing as a fallback if there is no jasmine config in package.json

[slackersoft]

Closed with #74