Skip to content
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

Custom Jasmine Reporters #193

Merged
merged 2 commits into from
Aug 18, 2016
Merged

Custom Jasmine Reporters #193

merged 2 commits into from
Aug 18, 2016

Conversation

juanger
Copy link
Contributor

@juanger juanger commented Apr 15, 2016

As part of the upgrade to Jasmine 2, the reporter functionality stopped to work, I added the feature back in a more generic approach. Essentially you bring your own reporters as assets and add them to the configuration file in this way:

reporters:
  junit:
    - "junit_reporter.js"
    - "junit_reporter.boot.js"

And then you can run guard with the --reporters junit flag

Removed junit options and replaced it with a more generic one to enable custom javascript jasmine reporters.

Documentation for reporters option.
@nathanstitt
Copy link
Member

Thanks @juanger - the custom reporters will be good to support. I'm going to merge this and then see if I can mixup the tests.

@nathanstitt nathanstitt merged commit 62a931b into guard:master Aug 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants