-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Reporter with all specs #564
Comments
You can write a different reporter. Currently there are Create a karma plugin. |
Renaming the issue. |
I have been using https://github.com/mlex/karma-spec-reporter to generate output very close to the desired one. |
I agree with @vojtajina that it is a good candidate for a separate reporter as the core framework will never be able to provide all the possible reporting outputs. Speaking of 3rd party plugins for Karma I was really surprised today to see that there are many, many plugins for Karma published on npm: https://www.npmjs.org/browse/keyword/karma-plugin. @vojtajina maybe we should devote create a dedicated page in the documentation that would list those 3rd party plugins? Similar to the way bower or others do? |
I would like to see a dedicated page for those 3rd party plugins. 👍 |
Closing in favor of karma-runner/karma-runner.github.com#30 |
I would like to see each spec in my Jasmine test and its status in the console when I run a test using Karma. As of now, all I get in the console is a total of executions and any errors that come out.
I need to see something like this:
I read the docs but I am unable to find a way to achieve this. Is there something i'm missing? If not, may I please put in an enhancement request?
Here is someone else asking the same question, on StackOverflow:
http://stackoverflow.com/questions/16684582/generate-jasmine-report-using-karma-runner
The answer gives some ways to work it out, but the second option he proposes would be the only option for this case. An option which I am not currently able to handle on my own.
The text was updated successfully, but these errors were encountered: