-
Notifications
You must be signed in to change notification settings - Fork 48
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
Output to File #60
Comments
Hey @csalazar1 Would love to know the use case? as the reporter is designed to send service messages to Teamcity which it expects on stdout of a build But because the reporter output goes to stdout and stderr if enabled you could do an output pipe to a file with something like |
@csalazar1 I can also recommend using
|
Thank you for the response guys! The use case is actually for someone that wants to have multiple reporters. In this case, the first reporter would be outputting to STDOUT and the second reporter, mocha-teamcity, should be outputting to log file. |
@csalazar1 in case if you want to have a several reporters, I would recommend you use https://github.com/stanleyhlng/mocha-multi-reporters. I had some experiments with this lib and another similar one, but found it much more useful. I think about using it even with one reporter because it allows to configure reporter options easier than several parameters in one line (i use CLI command for running tests). I just faced one issue when was configuring mocha-teamcity-reporter in mocha-multi-reporters - passing boolean value to report parameter. If I remember correctly, boolean value should be double quoted, like this: "true" (for mocha-teamcity-reporter! I did not face such issues with other reporters). Both reporters will output in the same place and should not hurt each other because you will use different reporters I believe. |
I have updated the readme with some of the highlights from this issue but if there is anything else to add please reopen with a comment. |
Is there no way to output results to file? I didn't see any under the options listed
The text was updated successfully, but these errors were encountered: