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

Way to get coverage report in HTML at the same time as console #118

Closed
briandela opened this issue Jul 16, 2014 · 5 comments · Fixed by #176
Closed

Way to get coverage report in HTML at the same time as console #118

briandela opened this issue Jul 16, 2014 · 5 comments · Fixed by #176
Assignees
Labels
Milestone

Comments

@briandela
Copy link
Contributor

@briandela briandela commented Jul 16, 2014

It would be great to be able to do something like

lab -vC -r console -r html:coverage.html

(-r html:coverage.html equivalent to '-r html -o coverage.html')

Right now I'm running the unit tests twice from a gulp task so I can see in my console how the tests are doing but also get the html report for coverage (I'm pushing it to a server to keep a record)

@briandela briandela closed this Jul 16, 2014
@briandela briandela reopened this Jul 16, 2014
@hueniverse hueniverse added the request label Aug 3, 2014
@hueniverse

This comment has been minimized.

Copy link
Member

@hueniverse hueniverse commented Aug 3, 2014

I'm not opposed to it, but wouldn't it be better to just add the content of the console to the html report?

@briandela

This comment has been minimized.

Copy link
Contributor Author

@briandela briandela commented Aug 21, 2014

The use case I'm thinking of is to get the nice, html CC report generated at the same time as running the tests in the console during my standard dev time. The HTML reports

For example, I have something similar to the makefile for lab, where I have multiple test commands, and when I want to run my tests to see the output and also have code coverage generated I essentially have to run all tests twice. It would be beneficial to be able to specify multiple reporters, or be able to specify to have a single reporter, and have CC report generated.

@briandela

This comment has been minimized.

Copy link
Contributor Author

@briandela briandela commented Aug 21, 2014

I guess, another way to look at it is that the current HTML reporter is more of a code coverage report than a test execution/result report.

@lloydbenson

This comment has been minimized.

Copy link
Contributor

@lloydbenson lloydbenson commented Aug 22, 2014

+1. The use case I have is that when I want to use multiple reporters, like adding a coverage report, seeing console output in a log and getting it in junit format for jenkins dashboards, I want it to be in the same run, with the same data set. This avoids issues of getting potentially different results for each reporter because you ran it again and it produced slightly different results (lets say you have a dependent service that isn't stable). It also speeds up the time, of simply not having to run the tests multiple times. I currently generate json results, and then copy the reporter functions to generate these different formats from the resulting json set so at least I am working with the same results.

@hueniverse

This comment has been minimized.

Copy link
Member

@hueniverse hueniverse commented Aug 23, 2014

My point is that the html reporter should be fixed to provide the information generated for both testing and coverage.

@geek geek self-assigned this Aug 25, 2014
@geek geek added this to the 4.2.0 milestone Aug 25, 2014
@arb arb closed this in #176 Aug 26, 2014
@Marsup Marsup added feature and removed request labels Sep 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.