-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
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
karma config should not use root dir #8
Comments
@musketyr huh... I'll have to think about this one. I think you could probably make the case for either way depending on how your project is set up. It's a default value and can be explicitly set to whatever you'd like, but ideally that default would work for most people. |
Well, if you run karmaRun in a project, you want to test just the given Dne út 9. 2. 2016 17:58 uživatel Craig Burke [email protected]
|
@musketyr that's a fair point. It probably would be a more reasonable default. |
I agree with @musketyr. Module root seems a better default. We're having the same issue. This forces us to repeat the module prefix in all config paths. Other than that, great plugin, thanks @craigburke |
in case of multiproject build you get the root directory of the very first parent
see https://github.com/craigburke/karma-gradle/blob/master/src/main/groovy/com/craigburke/gradle/KarmaPlugin.groovy#L106
therefor no tests are being executed
The text was updated successfully, but these errors were encountered: