-
Notifications
You must be signed in to change notification settings - Fork 95
Pass client config to mocha.setup #13
Comments
Now all configuration in `client.config.mocha` is passed to the setup method of mocha. The default ui style of `'bdd'` is still set if nothing else is supplied. Also the reporter will be always overridden as this needs to be our custom one. Fixes karma-runner#13.
Now all configuration in `client.config.mocha` is passed to the setup method of mocha. The default ui style of `'bdd'` is still set if nothing else is supplied. Also the reporter will be always overridden as this needs to be our custom one. Fixes karma-runner#13.
Now all configuration in `client.config.mocha` is passed to the setup method of mocha. The default ui style of `'bdd'` is still set if nothing else is supplied. Also the reporter will be always overridden as this needs to be our custom one. Fixes #13.
Seems that this is broken in v0.12.16:
My config file:
Let me know if I can include any more debug info. |
@Elijen Hi! I tried reproduce it on test project, Thanks! |
It woks for "karma start", but break in "grunt karma". |
@rickychien Nice catch! I can confirm that |
@rickychien, @Elijen thanks! I think need open issue in grunt-karma and I will try to see the error in more detail at the weekend. Can you create example project in which this error can be reproduced? |
Confirmed A quick hack to fix it is to include:
in the Gruntfile of |
Can you write karma settings from Thanks! |
So I changed the timeout setting in my karma configuration file already and it does work for
and Well, I think this issue tracking should go to grunt-karma, not grunt-mocha. |
Guys, since you looked into this one - is it an issue that should be fixed in this repo or is it something that rather belongs to the grunt plugin? |
close as obsolete |
Should do:
The text was updated successfully, but these errors were encountered: