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
Set default value for outputDir #54
Comments
Experienced the same issue here. I believe the rewrite from v0.2.2 to 0.3.x breaks this: |
If you want the old behaviour back, you can for now just set |
Thanks for feedback. It's good to know that setting outputDir to blank results in the old behavior WRT where the file is written. But, my suggestion is that the behavior should be like this by default ... that it should act as if outputDir is blank when it's not explicitly set. |
On my mac, the expression if (!reporterConfig.outputDir) evaluates to true with outputDir is set to ''. There doesn't seem to be a workaround in my case. |
Same problem here: !reporterConfig.outputDir evaluates to true on linux (Ubuntu 14.04) |
You could try by setting |
set default value of outputDir to '.', fixes #54
I just upgraded karma-junit-reporter from v0.2.2 to v0.3.3. Test runs fail with error: "You must set an output directory for JUnitReporter via the outputDir config property". It seems that this setting had a default value before, but is now required. Can we please revert to the default value? It was working just fine. Thanks.
The text was updated successfully, but these errors were encountered: